- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 18 for systemz (0.3 sec)
-
okhttp-tls/README.md
Call call = client.newCall(new Request.Builder() .url(server.url("/")) .build()); Response response = call.execute(); System.out.println(response.handshake().peerPrincipal()); RecordedRequest recordedRequest = server.takeRequest(); System.out.println(recordedRequest.getHandshake().peerPrincipal()); ``` This handshake is successful because each party has prearranged to trust the root certificate that
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Sun Dec 17 15:34:10 GMT 2023 - 9.1K bytes - Viewed (1) -
cni/README.md
#### From a specific node syslog The CNI plugins are executed by threads in the `kubelet` process. The CNI plugins logs end up the syslog under the `kubelet` process. On systems with `journalctl` the following is an example command line to view the last 1000 `kubelet` logs via the `less` utility to allow for `vi`-style searching: ```console $ journalctl -t kubelet -n 1000 | less ```
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Fri May 03 19:29:42 GMT 2024 - 12.3K bytes - Viewed (0) -
docs/bucket/notifications/README.md
## Publish MinIO events via AMQP Install RabbitMQ from [here](https://www.rabbitmq.com/). ### Step 1: Add AMQP endpoint to MinIO The AMQP configuration is located under the sub-system `notify_amqp` top-level key. Create a configuration key-value pair here for your AMQP instance. The key is a name for your AMQP endpoint, and the value is a collection of key-value parameters described in the table below. ``` KEY:
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 84K bytes - Viewed (2) -
manifests/charts/gateway/README.md
installation was done like: ```console helm install istio-ingress manifests/charts/gateways/istio-ingress -n istio-system ``` It could be upgraded with ```console helm upgrade istio-ingress manifests/charts/gateway -n istio-system --set name=istio-ingressgateway --set labels.app=istio-ingressgateway --set labels.istio=ingressgateway ```
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 19:38:07 GMT 2024 - 6.6K bytes - Viewed (0) -
docs/metrics/prometheus/README.md
``` ##### Node (optional) Optionally you can also collect per node metrics. This needs to be done on a per server instance. The scrape configurations should use all the servers under `targets` so that graphing systems like grafana can visualize them for all the nodes ```yaml scrape_configs: - job_name: minio-job metrics_path: /minio/v2/metrics/node scheme: http static_configs:
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 12 15:49:30 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/kms/README.md
# KMS Guide [![Slack](https://slack.min.io/slack?type=svg)](https://slack.min.io) MinIO uses a key-management-system (KMS) to support SSE-S3. If a client requests SSE-S3, or auto-encryption is enabled, the MinIO server encrypts each object with an unique object key which is protected by a master key managed by the KMS. ## Quick Start
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Thu Jan 18 07:03:17 GMT 2024 - 7.1K bytes - Viewed (0) -
README.md
<https://dl.min.io> and replace the existing MinIO binary let's say for example `/opt/bin/minio`, apply executable permissions `chmod +x /opt/bin/minio` and proceed to perform `mc admin service restart alias/`. - For installations using Systemd MinIO service, upgrade via RPM/DEB packages **parallelly** on all servers or replace the binary lets say `/opt/bin/minio` on all nodes, apply executable permissions `chmod +x /opt/bin/minio` and process to perform `mc admin service restart alias/`....
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Wed Feb 14 17:51:34 GMT 2024 - 18.7K bytes - Viewed (0) -
manifests/charts/README.md
and understand each binary that gets deployed, and select which combination to use. Note: each component can be installed in parallel with an existing Istio 1.0 or 1.1 installation in `istio-system`. The new components will not interfere with existing apps, but can interoperate, and it is possible to gradually move apps from Istio 1.0/1.1 to the new environments and across environments ( for example canary -> prod )
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) -
manifests/charts/istio-cni/README.md
```console helm install istio-cni istio/cni -n kube-system ``` Installation in `kube-system` is recommended to ensure the [`system-node-critical`](https://kubernetes.io/docs/tasks/administer-cluster/guaranteed-scheduling-critical-addon-pods/) `priorityClassName` can be used. You can install in other namespace only on K8S clusters that allow 'system-node-critical' outside of kube-system. ## Configuration
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 2.5K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/README.md
To install the chart with the release name `istiod`: ```console kubectl create namespace istio-system helm install istiod istio/istiod --namespace istio-system ``` ## Uninstalling the Chart To uninstall/delete the `istiod` deployment: ```console helm delete istiod --namespace istio-system ``` ## Configuration To view support configuration options and documentation, run: ```console
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Wed Jan 10 05:10:03 GMT 2024 - 2K bytes - Viewed (0)