Skip to content

e2e output: Increase signal-to-noise ratio by avoiding unhealthy conditions in wl-cluster #1674

@guettli

Description

@guettli

/kind feature

When running the e2e test, these warnings are visible:

kube-system pods cilium-operator-f8b67796c-mmk9l Condition PodScheduled=False Unschedulable "0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod." (4m16s)

cilium-operator is configured to run with two pods. I would like to change that one, so that this warning does not appear.


kube-system pods hubble-relay-595cd8cfb4-tv6xh Condition PodScheduled=False Unschedulable "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling." (4m16s)

I think running hubble-relay is not needed in e2e tests.

kube-system pods hubble-ui-7fd6bc845b-8wcxg Condition PodScheduled=False Unschedulable "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling." (4m16s)

Same here, running hubbl-ui is not needed in e2e test.


My goal: increase signal-to-noise ratio.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions