- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 122 for from (2.99 sec)
-
.github/ISSUE_TEMPLATE/tensorflow_issue_template.yaml
description: If compiling from source - type: input id: Compiler attributes: label: GCC/compiler version description: If compiling from source - type: input id: Cuda attributes: label: CUDA/cuDNN version - type: input id: Gpu attributes: label: GPU model and memory description: If compiling from source - type: textarea
Others - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Wed Jun 28 18:25:42 GMT 2023 - 3.7K bytes - Viewed (0) -
common/scripts/metallb-native.yaml
properties: interfaces: description: A list of interfaces to announce from. The LB IP will be announced only from these interfaces. If the field is not set, we advertise from all the interfaces on the host. items: type: string type: array ipAddressPoolSelectors:
Others - Registered: Wed May 01 22:53:12 GMT 2024 - Last Modified: Fri Feb 23 23:56:31 GMT 2024 - 63.9K bytes - Viewed (0) -
manifests/charts/default/templates/mutatingwebhook.yaml
# Adapted from istio-discovery/templates/mutatingwebhook.yaml # Removed paths for legacy and default selectors since a revision tag # is inherently created from a specific revision {{/* Copy just what we need to avoid expensive deepCopy */}} {{- $whv := dict "revision" .Values.revision "injectionURL" .Values.istiodRemote.injectionURL "namespace" .Release.Namespace }} {{- define "core" }} - name: {{.Prefix}}sidecar-injector.istio.io clientConfig:
Others - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 3.7K bytes - Viewed (0) -
istioctl/pkg/workload/testdata/vmconfig/ipv4/workloadgroup.yaml
kind: WorkloadGroup metadata: name: foo namespace: bar spec: metadata: annotations: proxy.istio.io/config: |- proxyMetadata: # this should override the value from the global meshconfig PROXY_CONFIG_ANNOT_VALUE: bar labels: {} template: ports: {} serviceAccount: vm-serviceaccount probe: httpGet:
Others - Registered: Wed May 01 22:53:12 GMT 2024 - Last Modified: Thu Jun 15 15:02:17 GMT 2023 - 377 bytes - Viewed (0) -
helm-releases/minio-4.0.3.tgz
to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or...
Others - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Fri Jul 08 06:16:22 GMT 2022 - 18K bytes - Viewed (0) -
helm-releases/minio-4.0.9.tgz
to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or...
Others - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Wed Aug 03 06:10:44 GMT 2022 - 18.6K bytes - Viewed (0) -
helm-releases/minio-4.0.11.tgz
to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or...
Others - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Sun Aug 07 05:41:47 GMT 2022 - 19.2K bytes - Viewed (0) -
helm-releases/minio-5.0.14.tgz
to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or...
Others - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Sat Sep 30 20:46:10 GMT 2023 - 20.6K bytes - Viewed (0) -
helm-releases/minio-4.0.15.tgz
to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or...
Others - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Wed Sep 21 11:07:01 GMT 2022 - 20K bytes - Viewed (0) -
helm-releases/minio-5.0.10.tgz
to add trust for MinIO's own CA and for the CA of a Keycloak server, a Kubernetes secret can be created from the certificate files using `kubectl`: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=public.crt --from-file=keycloak.crt ``` If TLS is not enabled, you would need only the third party CA: ``` kubectl -n minio create secret generic minio-trusted-certs --from-file=keycloak.crt ``` The name of the generated secret can then be passed to Helm using a values file or...
Others - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Sat May 27 00:05:49 GMT 2023 - 20.3K bytes - Viewed (0)