- Sort Score
- Result 10 results
- Languages All
Results 391 - 400 of 1,290 for tort (0.05 sec)
-
helm-releases/minio-3.1.6.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 }}...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Sep 23 19:56:39 UTC 2021 - 14.5K bytes - Viewed (0) -
api/maven-api-settings/src/main/mdo/settings.mdo
The proxy password. </description> <type>String</type> </field> <field xml.tagName="port"> <name>portString</name> <version>1.0.0+</version> <description> The proxy port. Note: While the type of this field is {@code String} for technical reasons, the semantic type is actually {@code int}. @see #getPort()
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Tue Oct 08 13:46:42 UTC 2024 - 33.5K bytes - Viewed (0) -
helm-releases/minio-3.1.9.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 }}...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Oct 10 21:28:04 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.3.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 }}...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Thu Nov 25 17:33:26 UTC 2021 - 14.6K bytes - Viewed (0) -
helm-releases/minio-3.4.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 }}...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Sun Dec 19 22:32:49 UTC 2021 - 14.8K bytes - Viewed (0) -
helm-releases/minio-3.4.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 }}...
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Mon Dec 20 21:11:50 UTC 2021 - 15.2K bytes - Viewed (0) -
common-protos/k8s.io/api/networking/v1beta1/generated.proto
// IngressPortStatus represents the error condition of a service port message IngressPortStatus { // port is the port number of the ingress port. optional int32 port = 1; // protocol is the protocol of the ingress port. // The supported values are: "TCP", "UDP", "SCTP" optional string protocol = 2; // error is to record the problem with the service port // The format of the error shall comply with the following rules:
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Mar 11 18:43:24 UTC 2024 - 14.9K bytes - Viewed (0) -
architecture/ambient/ztunnel.md
* It is critical that this path preserves the Service IP, if the traffic was to a Service. * All traffic *ingressing* a pod on port 15008 in the mesh is assumed to be HBONE, and should be redirected to the node-local ztunnel on port 15008 (more on this later).
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Jul 17 23:10:17 UTC 2024 - 16.8K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/query/TermQueryCommand.java
import org.opensearch.index.query.QueryBuilder; import org.opensearch.index.query.QueryBuilders; import org.opensearch.search.sort.SortOrder; public class TermQueryCommand extends QueryCommand { private static final Logger logger = LogManager.getLogger(TermQueryCommand.class); private static final String SORT_FIELD = "sort"; @Override protected String getQueryClassName() { return TermQuery.class.getSimpleName(); }
Registered: Thu Oct 31 13:40:30 UTC 2024 - Last Modified: Sat Oct 12 01:54:15 UTC 2024 - 10K bytes - Viewed (0) -
src/main/java/jcifs/smb1/http/NetworkExplorer.java
out.print( "<a class=\"sort\" style=\"width: " + maxLen + ";\" href=\"?fmt=detail&sort=name\">Name</a>" ); out.println( "<a class=\"sort\" href=\"?fmt=detail&sort=size\">Size</a>" ); out.println( "<a class=\"sort\" href=\"?fmt=detail&sort=type\">Type</a>" ); out.println( "<a class=\"sort\" style=\"width: 180\" href=\"?fmt=detail&sort=date\">Modified</a><br clear='all'><p>" );
Registered: Sun Nov 03 00:10:13 UTC 2024 - Last Modified: Wed Jan 22 03:57:31 UTC 2020 - 19.7K bytes - Viewed (0)