- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 15 for usaras (0.14 sec)
-
common-protos/k8s.io/api/certificates/v1beta1/generated.proto
// spec contains the certificate request, and is immutable after creation. // Only the request, signerName, expirationSeconds, and usages fields can be set on creation. // Other fields are derived by Kubernetes and cannot be modified by users. optional CertificateSigningRequestSpec spec = 2; // Derived information about the request. // +optional optional CertificateSigningRequestStatus status = 3;
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 6.7K bytes - Viewed (0) -
manifests/charts/README.md
policy/control/telemetry - so testing/staging of new settings and versions can be performed by a different role than the prod version. The intended users of this repo are users running Istio in production who want to select, tune and understand each binary that gets deployed, and select which combination to use.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Feb 07 17:53:24 GMT 2024 - 6.7K bytes - Viewed (0) -
cni/test/testdata/expected/ZZZ-istio-cni-kubeconfig.expected
users: - name: istio-cni user:
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Nov 19 23:19:19 GMT 2020 - 2.5K bytes - Viewed (0) -
manifests/charts/gateways/istio-ingress/templates/zzz_profile.yaml
Complex logic ahead... We have three sets of values, in order of precedence (last wins): 1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
RELEASE_BRANCHES.md
* Have installs and upgrades affected by this feature? * Is the feature still being worked on? * Is the default behavior altered? * Is this turned on by default? * How many users are affected by this change? ## Feature implementation Release managers will continue to have a final say in what gets merged or not, unless directed by the TOC. See the next
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Nov 12 23:27:43 GMT 2021 - 3.9K bytes - Viewed (0) -
common-protos/k8s.io/api/certificates/v1alpha1/generated.proto
// user in the cluster, because they can be mounted by pods using the // `clusterTrustBundle` projection. All service accounts have read access to // ClusterTrustBundles by default. Users who only have namespace-level access // to a cluster can read ClusterTrustBundles by impersonating a serviceaccount // that they have access to. // // It can be optionally associated with a particular assigner, in which case it
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 4.2K bytes - Viewed (0) -
cni/pkg/install/testdata/kubeconfig-newhost
server: https://50.76.2.1:443 name: local contexts: - context: cluster: local user: istio-cni name: istio-cni-context current-context: istio-cni-context kind: Config preferences: {} users: - name: istio-cni user:
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Aug 11 01:19:03 GMT 2023 - 1.7K bytes - Viewed (0) -
common-protos/k8s.io/api/authentication/v1/generated.proto
optional string error = 3; } // UserInfo holds the information about the user needed to implement the // user.Info interface. message UserInfo { // The name that uniquely identifies this user among all active users. // +optional optional string username = 1; // A unique value that identifies this user across time. If this user is // deleted and another user by the same name is added, they will have // different UIDs.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 6.7K bytes - Viewed (0) -
cni/pkg/install/testdata/kubeconfig-skip-tls
server: https://10.96.0.1:443 name: local contexts: - context: cluster: local user: istio-cni name: istio-cni-context current-context: istio-cni-context kind: Config preferences: {} users: - name: istio-cni user:
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed May 17 02:22:22 GMT 2023 - 342 bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/templates/zzz_profile.yaml
Complex logic ahead... We have three sets of values, in order of precedence (last wins): 1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0)