Skip to content

Should ignore unhealthy workload status in backend map #693

@hzxuzhonghu

Description

@hzxuzhonghu

What would you like to be added:

We should filter out unhealthy workload, and only store healthy ones to backend map.

When pod is being created or deleted, kmesh could receive workload with Status: WorkloadStatus_UNHEALTHY

Kube-proxy also filtered out unready endpoint when maintaining iptables.

If a pod access a server pod deleted/not ready, connection error or timeout may happen.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions