- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 59 for Users (0.15 sec)
-
manifests/charts/UPDATING-CHARTS.md
Helm charts `values.yaml` represent a complex user facing API that tends to grow uncontrollably over time due to design choices in Helm. The underlying Kubernetes resources we configure have 1000s of fields; given enough users and bespoke use cases, eventually someone will want to customize every one of those fields. If all fields are exposed in `values.yaml`, we end up with an massive API that is also likely worse than just using the Kubernetes API directly.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Jul 27 18:28:55 GMT 2023 - 3.2K 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) -
docker/iptables.yaml
- ip6tables - libnetfilter_conntrack - libnfnetlink - libmnl - libgcc archs: - x86_64 - aarch64 paths: - path: /run type: directory permissions: 0o755 accounts: users: - username: nonroot uid: 65532 - username: nobody uid: 65534 run-as: 65532
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu May 02 17:24:41 GMT 2024 - 541 bytes - Viewed (0) -
manifests/helm-profiles/README.md
Any changes to this folder should have a `make copy-templates` applied afterwards. Warning: unlike the `IstioOperator` profiles, these profiles cannot enable or disable certain components. As a result, users still need to ensure they install the appropriate charts to use a profile correctly.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 708 bytes - Viewed (0) -
cni/pkg/install/testdata/kubeconfig-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 - 1.7K bytes - Viewed (0) -
common-protos/k8s.io/api/authentication/v1beta1/generated.proto
repeated string items = 1; } // SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request. // When using impersonation, users will receive the user info of the user being impersonated. If impersonation or // request header authentication is used, any extra keys will have their case ignored and returned as lowercase. message SelfSubjectReview {
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 5.2K 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/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/gateway/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) -
manifests/charts/base/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)