- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 98 for localhost (0.36 sec)
-
cni/pkg/nodeagent/testdata/localhost.yaml
# This shows an example local config for ztunnel that adds a workload for localhost. # This allows local testing by sending requests through the local ztunnel to other servers running on localhost. workloads: - uid: cluster1//v1/Pod/default/local name: local namespace: default serviceAccount: default workloadIps: ["127.0.0.1"] protocol: HBONE node: local network: "" services: "default/example.com": 80: 8080
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Jan 26 20:34:28 GMT 2024 - 1.2K bytes - Viewed (0) -
.github/workflows/iam-integrations.yaml
go-version: [1.21.x] ldap: ["", "localhost:389"] etcd: ["", "http://localhost:2379"] openid: ["", "http://127.0.0.1:5556/dex"] exclude: # exclude combos where all are empty. - ldap: "" etcd: "" openid: "" # exclude combos where both ldap and openid IDPs are specified. - ldap: "localhost:389" openid: "http://127.0.0.1:5556/dex"
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Apr 25 15:49:53 GMT 2024 - 4.2K bytes - Viewed (0) -
istioctl/pkg/kubeinject/testdata/mesh-config.yaml
#interceptionMode: REDIRECT # # Port where Envoy listens (on local host) for admin commands # You can exec into the istio-proxy container in a pod and # curl the admin port (curl http://localhost:15000/) to obtain # diagnostic information from Envoy. See # https://lyft.github.io/envoy/docs/operations/admin.html # for more details proxyAdminPort: 15000 # # Zipkin trace collector zipkinAddress: ""
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Jun 15 15:02:17 GMT 2023 - 2.2K bytes - Viewed (0) -
helm-releases/minio-3.4.3.tgz
chart-1640120023-minio.minio.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace minio -l "release=chart-1640120023" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace minio Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/ You can now access MinIO server on http://localhost:9000. Follow the below steps to connect to MinIO server with mc...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Dec 21 20:55:50 GMT 2021 - 17.7K bytes - Viewed (0) -
manifests/charts/istiod-remote/files/injection-template.yaml
- POST - drain {{- end }} env: {{- if eq .InboundTrafficPolicyMode "localhost" }} - name: REWRITE_PROBE_LEGACY_LOCALHOST_DESTINATION value: "true" {{- end }} - name: PILOT_CERT_PROVIDER value: {{ .Values.global.pilotCertProvider }} - name: CA_ADDR
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Apr 26 16:51:17 GMT 2024 - 23.7K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/files/injection-template.yaml
- POST - drain {{- end }} env: {{- if eq .InboundTrafficPolicyMode "localhost" }} - name: REWRITE_PROBE_LEGACY_LOCALHOST_DESTINATION value: "true" {{- end }} - name: PILOT_CERT_PROVIDER value: {{ .Values.global.pilotCertProvider }} - name: CA_ADDR
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri Apr 26 16:51:17 GMT 2024 - 23.7K bytes - Viewed (1) -
helm-releases/minio-1.0.5.tgz
.Values.service.type "ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Aug 25 19:53:57 GMT 2021 - 13.6K bytes - Viewed (0) -
helm-releases/minio-3.0.0.tgz
.Values.service.type "ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 02 01:47:43 GMT 2021 - 13.8K bytes - Viewed (0) -
helm-releases/minio-3.0.1.tgz
.Values.service.type "ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Sep 02 01:47:43 GMT 2021 - 13.8K bytes - Viewed (0) -
helm-releases/minio-1.0.4.tgz
.Values.service.type "ClusterIP" "NodePort" }} Minio can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access Minio from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Aug 25 02:12:51 GMT 2021 - 13.6K bytes - Viewed (0)