Skip to content
This repository was archived by the owner on Jan 11, 2023. It is now read-only.
This repository was archived by the owner on Jan 11, 2023. It is now read-only.

Kubernetes - Node in FullDisruption #220

Description

@otaviosoares

I noticed some of my pods were crashing last night. Checking kube-controller logs I found the following:

I0126 01:03:24.264593 1 nodecontroller.go:608] NodeController detected that zone brazilsouth::2 is now in state FullDisruption.

After that one node and the master went NotReady:

I0126 01:03:23.414900       1 controller_utils.go:285] Recording status change NodeNotReady event message for node k8s-agentpool1-36264260-1
I0126 01:03:23.415838       1 event.go:217] Event(api.ObjectReference{Kind:"Node", Namespace:"", Name:"k8s-agentpool1-36264260-1", UID:"225a405a-cbbf-11e6-af05-000d3ac07eea", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'NodeNotReady' Node k8s-agentpool1-36264260-1 status is now: NodeNotReady
I0126 01:03:29.856260       1 controller_utils.go:285] Recording status change NodeNotReady event message for node k8s-master-36264260-0
I0126 01:03:29.858142       1 event.go:217] Event(api.ObjectReference{Kind:"Node", Namespace:"", Name:"k8s-master-36264260-0", UID:"23e03ca4-cbbf-11e6-af05-000d3ac07eea", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'NodeNotReady' Node k8s-master-36264260-0 status is now: NodeNotReady

What does the FullDisruption mean? Is it a failure on Azure itself or on the k8s side? I couldn't find any failure report by Azure in the given timestamp. I've also checked my vms hardware monitoring and there is nothing that raises an eye.

Thanks

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    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