Skip to content

Explain in detail how the healthchecks work #301

@raphaeltm

Description

@raphaeltm

Right now there's a thing that can easily trip up a user. We take the container healthcheck and turn that into two different healthchecks: the target group health check which sends an http request to a path on the task, and an ECS healthcheck which executes the command (as I understand it).

So a user who has, for example, forgotten to install curl in their container, they might see 200 status codes show up from the LB healthchecks and think everything is fine, and be confused about why their services fails to deploy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions