- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 57 for restarts (0.62 sec)
-
docs/en/docs/deployment/concepts.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 18K bytes - Viewed (0) -
docs/en/docs/deployment/server-workers.md
From the list of deployment concepts from above, using workers would mainly help with the **replication** part, and a little bit with the **restarts**, but you still need to take care of the others: * **Security - HTTPS** * **Running on startup** * ***Restarts*** * Replication (the number of processes running) * **Memory** * **Previous steps before starting** ## Containers and Docker
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 9.1K bytes - Viewed (0) -
docs/en/docs/deployment/docker.md
## Running on Startup and Restarts There is normally another tool in charge of **starting and running** your container. It could be **Docker** directly, **Docker Compose**, **Kubernetes**, a **cloud service**, etc. In most (or all) cases, there's a simple option to enable running the container on startup and enabling restarts on failures. For example, in Docker, it's the command line option `--restart`.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 34K bytes - Viewed (0) -
docs/en/docs/deployment/manually.md
This is the basic idea. But you will probably want to take care of some additional things, like: * Security - HTTPS * Running on startup * Restarts * Replication (the number of processes running) * Memory * Previous steps before starting
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 9.2K bytes - Viewed (0) -
cmd/admin-handlers.go
// ---------- // Supports following actions: // - restart (restarts all the MinIO instances in a setup) // - stop (stops all the MinIO instances in a setup) // - freeze (freezes all incoming S3 API calls) // - unfreeze (unfreezes previously frozen S3 API calls) // // This newer API now returns back status per remote peer and local regarding // if a "restart/stop" was successful or not. Service signal now supports
Go - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Mon Apr 29 17:39:04 GMT 2024 - 97.8K bytes - Viewed (2) -
helm/minio/values.yaml
additionalAnnotations: {} ## Typically the deployment/statefulset includes checksums of secrets/config, ## So that when these change on a subsequent helm install, the deployment/statefulset ## is restarted. This can result in unnecessary restarts under GitOps tooling such as ## flux, so set to "true" to disable this behaviour. ignoreChartChecksums: false ## Additional arguments to pass to minio binary extraArgs: []
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun Apr 28 10:14:37 GMT 2024 - 18.4K bytes - Viewed (0) -
cni/README.md
- it also sets up a UDS socket for istio-cni to send logs to this container. - based on config, it may run the 'repair' controller that detects pods where istio setup fails and restarts them, or created in corner cases. - if ambient is enabled, also runs an ambient controller, watching Pod, Namespace - `istio-cni` - CNI plugin executable copied to `/opt/cni/bin`
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) -
helm-releases/minio-5.2.0.tgz
with deployment or statefulset additionalAnnotation: {} ## Typically the deployment/statefulset includes checksums of secrets/config, ## So that when these change on a subsequent helm install, the deployment/statefulset ## is restarted. This can result in unnecessary restarts under GitOps tooling such as ## flux, so set to "true" to disable this behaviour. ignoreChartChecksums: false ## Additional arguments to pass to minio binary extraArgs: [] # example for enabling FTP: # - --ftp=\"address=:8021\"...
Others - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Sun Apr 28 10:14:37 GMT 2024 - 21.7K bytes - Viewed (0) -
build-logic/documentation/src/main/groovy/gradlebuild/docs/ServeDocs.java
builder.setArgs(Arrays.asList("-p", getPort().get(), "-d", getDocsDirectory().get().getAsFile().getAbsolutePath())); registry.start(getPath(), DeploymentRegistry.ChangeBehavior.RESTART, JavaApplicationHandle.class, builder); } } @Inject protected abstract DeploymentRegistry getDeploymentRegistry(); @Inject
Java - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Thu Apr 18 12:38:47 GMT 2024 - 2.9K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.30.md
- Fixed an issue where the `configmap`, `secret`, `projected`, and `downwardAPI` volume types didn't create user-visible files after a kubelet restart. This fix ensures data persistence and accessibility after restarts. ([#122807](https://github.com/kubernetes/kubernetes/pull/122807), [@carlory](https://github.com/carlory))
Plain Text - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Wed Apr 17 17:56:15 GMT 2024 - 227.9K bytes - Viewed (0)