Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 16 for FallbackToLogsOnError (0.53 sec)

  1. staging/src/k8s.io/apimachinery/pkg/util/managedfields/internal/testdata/swagger.json

              "description": "Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.",...
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Tue Feb 20 15:45:02 UTC 2024
    - 229.4K bytes
    - Viewed (0)
  2. CHANGELOG/CHANGELOG-1.6.md

        IOPS.
      - Ignore `.mount` cgroups, fixing disappearing stats.
    * A new field `terminationMessagePolicy` has been added to containers that allows
      a user to request FallbackToLogsOnError, which will read from the container's
      logs to populate the termination message if the user does not write to the
      termination message log file. The termination message file is now properly
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Thu Dec 24 02:28:26 UTC 2020
    - 304K bytes
    - Viewed (0)
  3. staging/src/k8s.io/api/core/v1/types.go

    	// for the container status message when the container exits with an error and the
    	// terminationMessagePath has no contents.
    	TerminationMessageFallbackToLogsOnError TerminationMessagePolicy = "FallbackToLogsOnError"
    )
    
    // Capability represent POSIX capabilities type
    type Capability string
    
    // Adds and removes POSIX capabilities from running containers.
    type Capabilities struct {
    	// Added capabilities
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed May 29 22:40:29 UTC 2024
    - 390.8K bytes
    - Viewed (0)
  4. common-protos/k8s.io/api/core/v1/generated.proto

      // Indicate how the termination message should be populated. File will use the contents of
      // terminationMessagePath to populate the container status message on both success and failure.
      // FallbackToLogsOnError will use the last chunk of container log output if the termination
      // message file is empty and the container exited with an error.
      // The log output is limited to 2048 bytes or 80 lines, whichever is smaller.
    Registered: Fri Jun 14 15:00:06 UTC 2024
    - Last Modified: Mon Mar 11 18:43:24 UTC 2024
    - 255.8K bytes
    - Viewed (0)
  5. staging/src/k8s.io/api/core/v1/types_swagger_doc_generated.go

    	"terminationMessagePolicy": "Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.",...
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed May 29 22:40:29 UTC 2024
    - 254.8K bytes
    - Viewed (0)
  6. CHANGELOG/CHANGELOG-1.17.md

    - If container fails because ContainerCannotRun, do not utilize the FallbackToLogsOnError TerminationMessagePolicy, as it masks more useful logs. ([#81280](https://github.com/kubernetes/kubernetes/pull/81280), [@yqwang-ms](https://github.com/yqwang-ms))
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Thu Jan 28 10:44:33 UTC 2021
    - 346.2K bytes
    - Viewed (0)
  7. staging/src/k8s.io/api/core/v1/generated.proto

      // Indicate how the termination message should be populated. File will use the contents of
      // terminationMessagePath to populate the container status message on both success and failure.
      // FallbackToLogsOnError will use the last chunk of container log output if the termination
      // message file is empty and the container exited with an error.
      // The log output is limited to 2048 bytes or 80 lines, whichever is smaller.
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed May 29 22:40:29 UTC 2024
    - 280.3K bytes
    - Viewed (0)
  8. api/openapi-spec/v3/apis__batch__v1_openapi.json

                "description": "Indicate how the termination message should be populated. File will use the contents of terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.",...
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed Jun 05 18:37:07 UTC 2024
    - 485.4K bytes
    - Viewed (0)
  9. pkg/generated/openapi/zz_generated.openapi.go

    terminationMessagePath to populate the container status message on both success and failure. FallbackToLogsOnError will use the last chunk of container log output if the termination message file is empty and the container exited with an error. The log output is limited to 2048 bytes or 80 lines, whichever is smaller. Defaults to File. Cannot be updated.\n\nPossible enum values:\n - `\"FallbackToLogsOnError\"` will read the most recent contents of the container logs for the container status message...
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed Jun 05 18:37:07 UTC 2024
    - 3M bytes
    - Viewed (0)
  10. pkg/apis/core/types.go

    	// for the container status message when the container exits with an error and the
    	// terminationMessagePath has no contents.
    	TerminationMessageFallbackToLogsOnError TerminationMessagePolicy = "FallbackToLogsOnError"
    )
    
    // Capability represent POSIX capabilities type
    type Capability string
    
    // Capabilities represent POSIX capabilities that can be added or removed to a running container.
    Registered: Sat Jun 15 01:39:40 UTC 2024
    - Last Modified: Wed May 29 22:40:29 UTC 2024
    - 268.9K bytes
    - Viewed (0)
Back to top