Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Custom Resource state should never be NIL or empty string for the operators

Description

When Custom Resource is created for the operator, Status is captured in the field “Status”. State should never be an empty string or NIL. This breaks lot of monitoring flow and also keeps the user not knowing on what’s happening or if something is stuck.

Ideally the status could be more realistic by giving current scenario.However to start with it should not be empty or NIL.

Example: Observed in PG operator, backup status is not known even after 2 mins. It should have been Initializing etc from the moment object was created. This should be checked for all the operators. If this is already addressed in the latest versions of the operator. Please ignore this ticket.

cc

$ kubectl get pg-backup NAME CLUSTER REPO DESTINATION STATUS TYPE COMPLETED AGE backup2 cluster1 repo2 2m23s cluster1-backup-lr7r-8zns4 cluster1 repo1 Succeeded full 7d21h 7d21h cluster1-repo1-full-zsgh5 cluster1 repo1 Succeeded full 4d10h 4d10h

Environment

None

Activity

Show:

Details

Assignee

Reporter

Needs QA

Yes

Priority

Smart Checklist

Created November 27, 2024 at 10:45 AM
Updated November 27, 2024 at 10:45 AM
Configure

Flag notifications