Skip to content

Misleading "Mondoo Operator controller is unavailable" message #1236

Description

@philipbalinov

On startup, the operator checks if the container's ContainerStatus.LastTerminationState.Terminated != nil, i.e. if the previous container exited with a non-zero error code.
If yes, the operator sets itself in a "degraded mode" and the following error is displayed in the UI:

Image

Until the pod restarts again, and the ContainerStatus.LastTerminationState is cleared, that banner will appear in the UI and report the integration in an error state.

In the case in question, the operator briefly lost connectivity with the KubeAPI, which caused it to panic and exit with a an error code 2. The next container span up just fine and ran for days, reporting the operator in a degraded state because of that one error.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions