Search Options

Results per page
Sort
Preferred Languages
Advance

Results 201 - 210 of 305 for Upgrade (0.23 sec)

  1. CHANGELOG/CHANGELOG-1.3.md

        * In order to safely upgrade an existing Kubernetes cluster without interruption of volume attach/detach logic:
            * First upgrade the master to Kubernetes v1.3.
                * This will start the new attach/detach controller.
    Registered: Fri Dec 26 09:05:12 UTC 2025
    - Last Modified: Thu Dec 24 02:28:26 UTC 2020
    - 84K bytes
    - Viewed (0)
  2. helm-releases/minio-3.4.3.tgz

    values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Dec 21 20:55:50 UTC 2021
    - 17.7K bytes
    - Viewed (0)
  3. src/main/java/jcifs/smb/NtlmPasswordAuthenticator.java

            // Log warning for insecure NTLMv1 usage
            if (compatibility < 3) {
                log.warn("Using insecure NTLMv1 authentication (LM compatibility level {}). "
                        + "Please upgrade to NTLMv2 by setting jcifs.smb.lmCompatibility to 3 or higher.", compatibility);
            }
    
            switch (compatibility) {
            case 0:
            case 1:
                // NTLMv1 - deprecated and insecure
    Registered: Sat Dec 20 13:44:44 UTC 2025
    - Last Modified: Sun Aug 31 08:00:57 UTC 2025
    - 30.3K bytes
    - Viewed (0)
  4. CHANGELOG/CHANGELOG-1.14.md

    - [Kubernetes v1.14 Release Notes](#kubernetes-v114-release-notes)
      - [1.14 What’s New](#114-whats-new)
      - [Known Issues](#known-issues-1)
      - [Urgent Upgrade Notes](#urgent-upgrade-notes)
        - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade)
      - [Deprecations](#deprecations)
      - [Removed and deprecated metrics](#removed-and-deprecated-metrics)
        - [Removed metrics](#removed-metrics)
    Registered: Fri Dec 26 09:05:12 UTC 2025
    - Last Modified: Mon Jun 14 22:06:39 UTC 2021
    - 271.5K bytes
    - Viewed (0)
  5. src/main/resources/fess_label_en.properties

    labels.user_gidNumber=gidNumber
    labels.group_gidNumber=gidNumber
    labels.gidNumber=gidNumber
    labels.user_homeDirectory=Home Directory
    labels.homeDirectory=Home Directory
    labels.upgrade_title_configuration=Upgrade
    labels.upgrade_data_migration=Data Migration
    labels.upgrade_reindex=Re-indexing
    labels.upgrade_start_button=Start
    labels.replace_aliases=Replace Aliases
    labels.reset_dictionaries=Reset Dictionaries
    Registered: Sat Dec 20 09:19:18 UTC 2025
    - Last Modified: Sat Dec 13 02:21:17 UTC 2025
    - 44K bytes
    - Viewed (0)
  6. apache-maven/src/assembly/maven/bin/mvn.cmd

    "%JAVACMD%" --enable-native-access=ALL-UNNAMED -version >nul 2>&1
    if ERRORLEVEL 1 (
        echo Error: Apache Maven 4.x requires Java 17 or newer to run. >&2
        "%JAVACMD%" -version >&2
        echo Please upgrade your Java installation or set JAVA_HOME to point to a compatible JDK. >&2
        goto error
    )
    
    :chkMHome
    set "MAVEN_HOME=%~dp0"
    set "MAVEN_HOME=%MAVEN_HOME:~0,-5%"
    if "%MAVEN_HOME%"=="" goto error
    
    :checkMCmd
    Registered: Sun Dec 28 03:35:09 UTC 2025
    - Last Modified: Wed Dec 10 16:40:06 UTC 2025
    - 10.7K bytes
    - Viewed (3)
  7. helm-releases/minio-3.0.1.tgz

    values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Thu Sep 02 01:47:43 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  8. helm-releases/minio-3.0.2.tgz

    values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Sep 03 08:11:32 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  9. helm-releases/minio-3.1.0.tgz

    values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Sep 12 18:19:27 UTC 2021
    - 14.3K bytes
    - Viewed (0)
  10. helm-releases/minio-3.1.1.tgz

    values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Mon Sep 13 16:43:10 UTC 2021
    - 14.3K bytes
    - Viewed (0)
Back to top