Skip to content

[failure mode] revisions that fail to scale up from 0 should set Ready=False #11531

Open

Description

@dprotaso

After a successful initial deploy and scale to zero - if a revision were to fail to scale from 0 a second time we should mark Ready=False.

This intent of this issue is to confirm what is the current behaviour is when readiness & liveness probes fail.

Activity

  1. added this to the 0.24.x milestone on Jun 15, 2021
  2. julz commented on Jun 25, 2021

    @julz
    Contributor

    /area api
    /kind spec
    /triage accepted

  3. added
    area/APIAPI objects and controllers
    kind/specDiscussion of how a feature should be exposed to customers.
    triage/acceptedIssues which should be fixed (post-triage)
    on Jun 25, 2021
  4. modified the milestones: 0.24.x, 0.25.x on Jul 6, 2021
  5. modified the milestones: 0.25.x, 0.26.x on Aug 26, 2021
  6. modified the milestones: 0.26.x, 0.27.x on Oct 6, 2021
  7. modified the milestones: v1.0.0, v1.1.0 on Nov 3, 2021
  8. modified the milestones: v1.1.0, v1.2.0 on Jan 4, 2022
  9. modified the milestones: v1.2.0, v1.3.0 on Feb 2, 2022
  10. modified the milestones: v1.3.0, v1.4.0 on Mar 10, 2022
  11. psschwei commented on Apr 7, 2022

    @psschwei
    Member

    /assign

  12. psschwei commented on Apr 7, 2022

    @psschwei
    Member

    whoops, was in the wrong tab
    /unassign

  13. modified the milestones: v1.4.0, v1.5.0 on May 10, 2022
  14. modified the milestones: v1.5.0, Icebox on Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/APIAPI objects and controllerskind/specDiscussion of how a feature should be exposed to customers.triage/acceptedIssues which should be fixed (post-triage)

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions