apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-46-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-46.ec2.internal
      uid: c739d823-a52b-4089-8e03-ec241c8c3e4c
    resourceVersion: "52491"
    uid: 93faef6d-8d4d-4703-b17f-338c852a311f
  spec:
    sourcePod: network-check-source-56d84b9f44-g5x79
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:32:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.101µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T20:00:52Z"
    - latency: 930.5µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:59:52Z"
    - latency: 999.563µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:58:52Z"
    - latency: 820.175µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:57:52Z"
    - latency: 1.081278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:56:52Z"
    - latency: 1.215748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:55:52Z"
    - latency: 869.803µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:54:52Z"
    - latency: 995.631µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:53:52Z"
    - latency: 1.047803ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:52:52Z"
    - latency: 888.696µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:51:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-46-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-46.ec2.internal
      uid: c739d823-a52b-4089-8e03-ec241c8c3e4c
    resourceVersion: "46983"
    uid: 7626befd-44bd-4c83-b5eb-4e56e9d52409
  spec:
    sourcePod: network-check-source-56d84b9f44-g5x79
    targetEndpoint: ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:31:52Z"
      message: 'load-balancer-api-external: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.834827ms
      message: 'load-balancer-api-external: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:55:52Z"
    - latency: 9.56463ms
      message: 'load-balancer-api-external: resolved host name ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:55:52Z"
    - latency: 4.473536ms
      message: 'load-balancer-api-external: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:54:52Z"
    - latency: 8.524471ms
      message: 'load-balancer-api-external: resolved host name ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:54:52Z"
    - latency: 5.083559ms
      message: 'load-balancer-api-external: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:53:52Z"
    - latency: 9.088476ms
      message: 'load-balancer-api-external: resolved host name ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:53:52Z"
    - latency: 4.891749ms
      message: 'load-balancer-api-external: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:52:52Z"
    - latency: 8.236868ms
      message: 'load-balancer-api-external: resolved host name ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:52:52Z"
    - latency: 5.06823ms
      message: 'load-balancer-api-external: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:51:52Z"
    - latency: 9.131359ms
      message: 'load-balancer-api-external: resolved host name ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:51:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-46-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-46.ec2.internal
      uid: c739d823-a52b-4089-8e03-ec241c8c3e4c
    resourceVersion: "46982"
    uid: abc598bb-105d-4980-a5ae-cff90809747f
  spec:
    sourcePod: network-check-source-56d84b9f44-g5x79
    targetEndpoint: ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:31:52Z"
      message: 'load-balancer-api-internal: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.595727ms
      message: 'load-balancer-api-internal: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:55:52Z"
    - latency: 9.598462ms
      message: 'load-balancer-api-internal: resolved host name ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:55:52Z"
    - latency: 4.793304ms
      message: 'load-balancer-api-internal: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:54:52Z"
    - latency: 8.441826ms
      message: 'load-balancer-api-internal: resolved host name ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:54:52Z"
    - latency: 4.408295ms
      message: 'load-balancer-api-internal: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:53:52Z"
    - latency: 8.980334ms
      message: 'load-balancer-api-internal: resolved host name ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:53:52Z"
    - latency: 4.860043ms
      message: 'load-balancer-api-internal: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:52:52Z"
    - latency: 8.147689ms
      message: 'load-balancer-api-internal: resolved host name ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:52:52Z"
    - latency: 5.044286ms
      message: 'load-balancer-api-internal: tcp connection to ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:51:52Z"
    - latency: 9.053623ms
      message: 'load-balancer-api-internal: resolved host name ae0315d6527da43fa90bb7e24f9d5564-5eebda5b60925409.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:51:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-46-to-network-check-target-ip-10-0-128-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-46.ec2.internal
      uid: c739d823-a52b-4089-8e03-ec241c8c3e4c
    resourceVersion: "52488"
    uid: 4d1a907f-1e8c-4406-b851-18c061780144
  spec:
    sourcePod: network-check-source-56d84b9f44-g5x79
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:32:52Z"
      message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 820.291µs
      message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T20:00:52Z"
    - latency: 1.285681ms
      message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:59:52Z"
    - latency: 1.055683ms
      message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:58:52Z"
    - latency: 695.926µs
      message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:57:52Z"
    - latency: 1.046559ms
      message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:56:52Z"
    - latency: 805.394µs
      message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:55:52Z"
    - latency: 1.271776ms
      message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:54:52Z"
    - latency: 808.519µs
      message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:53:52Z"
    - latency: 792.405µs
      message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:52:52Z"
    - latency: 845.77µs
      message: 'network-check-target-ip-10-0-128-46: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:51:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-46-to-network-check-target-ip-10-0-138-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-46.ec2.internal
      uid: c739d823-a52b-4089-8e03-ec241c8c3e4c
    resourceVersion: "52489"
    uid: aa8cda09-c07d-4284-b1dd-dc1c70b5cf4e
  spec:
    sourcePod: network-check-source-56d84b9f44-g5x79
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:32:52Z"
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.93963ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T20:00:52Z"
    - latency: 2.427801ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:59:52Z"
    - latency: 2.191554ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:58:52Z"
    - latency: 2.092415ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:57:52Z"
    - latency: 2.253879ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:56:52Z"
    - latency: 1.884451ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:55:52Z"
    - latency: 2.351637ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:54:52Z"
    - latency: 2.326759ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:53:52Z"
    - latency: 2.355868ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:52:52Z"
    - latency: 2.21983ms
      message: 'network-check-target-ip-10-0-138-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:51:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-46-to-network-check-target-ip-10-0-143-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-46.ec2.internal
      uid: c739d823-a52b-4089-8e03-ec241c8c3e4c
    resourceVersion: "52490"
    uid: 5b5cd3c1-6120-44db-be45-062ef5c3fdee
  spec:
    sourcePod: network-check-source-56d84b9f44-g5x79
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:32:52Z"
      message: 'network-check-target-ip-10-0-143-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.127325ms
      message: 'network-check-target-ip-10-0-143-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T20:00:52Z"
    - latency: 2.019795ms
      message: 'network-check-target-ip-10-0-143-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:59:52Z"
    - latency: 2.140538ms
      message: 'network-check-target-ip-10-0-143-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:58:52Z"
    - latency: 2.092183ms
      message: 'network-check-target-ip-10-0-143-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:57:52Z"
    - latency: 1.903577ms
      message: 'network-check-target-ip-10-0-143-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:56:52Z"
    - latency: 1.988679ms
      message: 'network-check-target-ip-10-0-143-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:55:52Z"
    - latency: 1.879163ms
      message: 'network-check-target-ip-10-0-143-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:54:52Z"
    - latency: 2.157822ms
      message: 'network-check-target-ip-10-0-143-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:53:52Z"
    - latency: 1.913862ms
      message: 'network-check-target-ip-10-0-143-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:52:52Z"
    - latency: 2.235338ms
      message: 'network-check-target-ip-10-0-143-55: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:51:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-02T19:25:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-46-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-46.ec2.internal
      uid: c739d823-a52b-4089-8e03-ec241c8c3e4c
    resourceVersion: "46981"
    uid: 14fe74a2-3b72-4f66-aaa3-10691d26568b
  spec:
    sourcePod: network-check-source-56d84b9f44-g5x79
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-02T19:31:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.908µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:55:52Z"
    - latency: 1.892486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:55:52Z"
    - latency: 737.248µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:54:52Z"
    - latency: 1.695997ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:54:52Z"
    - latency: 1.275792ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:53:52Z"
    - latency: 2.005668ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:53:52Z"
    - latency: 873.509µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:52:52Z"
    - latency: 1.619682ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:52:52Z"
    - latency: 953.883µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-02T19:51:52Z"
    - latency: 1.80348ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-02T19:51:52Z"
kind: List
metadata:
  resourceVersion: ""