Skip to content

Deprecated conditions possibly incoherent #2009

@perdasilva

Description

@perdasilva

The *Deprecated conditions report a status of False with reason Deprecated. Should it not be, Not deprecated?

{
    "lastTransitionTime": "2025-06-03T07:52:54Z",
    "message": "",
    "observedGeneration": 1,
    "reason": "Deprecated",
    "status": "False",
    "type": "Deprecated"
},
{
    "lastTransitionTime": "2025-06-03T07:52:54Z",
    "message": "",
    "observedGeneration": 1,
    "reason": "Deprecated",
    "status": "False",
    "type": "PackageDeprecated"
},
{
    "lastTransitionTime": "2025-06-03T07:52:54Z",
    "message": "",
    "observedGeneration": 1,
    "reason": "Deprecated",
    "status": "False",
    "type": "ChannelDeprecated"
},
{
    "lastTransitionTime": "2025-06-03T07:52:54Z",
    "message": "",
    "observedGeneration": 1,
    "reason": "Deprecated",
    "status": "False",
    "type": "BundleDeprecated"
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions