Jump to Content
SaladCloud
HomeGuidesAPI ReferenceChangelog
Log InSaladCloud
Log In
HomeGuidesAPI ReferenceChangelog

Getting Started

  • Salad Container Engine (SCE)
    • Containers
  • Using The API

Salad Container Engine

  • How to Deploy a Container with Salad Portal
  • The Deployment Lifecycle
  • Managing Deployments
  • Container Registries
    • Google Container Registry
    • Azure Container Registry
    • Dockerhub
    • Amazon Elastic Container Registry (ECR)
  • Networking
    • Enabling IPv6 for inbound networking
    • Sending requests to your container
  • External Logging
    • Using TCP
    • New Relic
  • Health Probes
    • Startup Probes
    • Liveness Probes

Recipes

  • Using Recipes
    • How To Use Stable Diffusion 2.1

Salad Gateway Service

  • Using HTTP CONNECT (Recommended)
  • Using HAproxy PROXY v2 Protocol
  • Requesting a Node Removal
  • Approved Domains
  • Smart Routing

Guides

  • Beta Signup Guide
    • Register on Salad Portal
    • Creating Organizations
    • Set Up a Project
    • Request Resources
  • How to Deploy a Container Group with the Public API

About

  • Billing
  • Quotas
  • SaladCloud Portal
Powered by 

Liveness Probes

Overview

Liveness probes are similar to startup probes, except that they run after the startup probe has completed successfully. Typically, Liveness probes are used to evaluate whether the application running in your container is in a healthy state.

Configuration

Fill the checkbox to enable the liveness probe. Currently, exec is the only supported protocol. Note that all fields are required.

Updated 16 days ago


  • Table of Contents
    • Overview
    • Configuration