Skip to content

use finalizers avoid losing deletions #450

Closed

Description

@redbaron

When Postgres CR is deleted it triggers deletion routine, which might not end completely due to crash, misconfiguration or intermittent Kubernetes errors. To be able to finish cleanup on restart, Postgres CR should remain present up until deletion is completed.

Kubernetes solutions for that is to use finalizers where resources is still present and queryable until all finalizers are completed. This would allow operator to continue cleanup routine on restart

Activity

  1. changed the title [-]use finalizers avoid loosing deletions[/-] [+]use finalizers avoid losing deletions[/+] on Jan 11, 2019
  2. FxKu commented on Apr 5, 2019

    @FxKu
    Contributor

    related to #387 and #551

  3. frittentheke commented on Jan 9, 2020

    @frittentheke
    Contributor

    @redbaron thanks for opening this ... I was just about to suggest this myself ;-)

    Another use case for finalizers would be a final pg_basebackup or logical backup before the cluster is annihilated by the operator for good - Just like AWS does with their final snapshot upon deletion of and RDS instance: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_DeleteInstance.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions