apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T16:16:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-64-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-64.ec2.internal
      uid: 43c100ce-ce0b-4fd6-8c1e-d52b5b014ddf
    resourceVersion: "214877"
    uid: 0a635e52-c1f1-4280-8506-23c607332945
  spec:
    sourcePod: network-check-source-6f78d59f99-cm2k2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T16:23:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.384724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:01:27Z"
    - latency: 1.10968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:00:27Z"
    - latency: 1.259795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:59:27Z"
    - latency: 1.295086ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:27Z"
    - latency: 1.401211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:27Z"
    - latency: 4.905599ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:27Z"
    - latency: 1.206297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:55:27Z"
    - latency: 1.184141ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:54:27Z"
    - latency: 1.465074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:53:27Z"
    - latency: 1.317528ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:52:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T16:16:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-64-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-64.ec2.internal
      uid: 43c100ce-ce0b-4fd6-8c1e-d52b5b014ddf
    resourceVersion: "212143"
    uid: d13c9e9e-0da9-4f41-a61b-e3b61cbf6570
  spec:
    sourcePod: network-check-source-6f78d59f99-cm2k2
    targetEndpoint: a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T16:22:27Z"
      message: 'load-balancer-api-external: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.659485ms
      message: 'load-balancer-api-external: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:27Z"
    - latency: 7.263653ms
      message: 'load-balancer-api-external: resolved host name a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:58:27Z"
    - latency: 13.260016ms
      message: 'load-balancer-api-external: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:27Z"
    - latency: 6.632148ms
      message: 'load-balancer-api-external: resolved host name a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:57:27Z"
    - latency: 18.665389ms
      message: 'load-balancer-api-external: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:27Z"
    - latency: 50.219688ms
      message: 'load-balancer-api-external: resolved host name a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:56:27Z"
    - latency: 17.55058ms
      message: 'load-balancer-api-external: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:55:27Z"
    - latency: 6.304523ms
      message: 'load-balancer-api-external: resolved host name a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:55:27Z"
    - latency: 15.704481ms
      message: 'load-balancer-api-external: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:54:27Z"
    - latency: 6.7964ms
      message: 'load-balancer-api-external: resolved host name a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:54:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T16:16:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-64-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-64.ec2.internal
      uid: 43c100ce-ce0b-4fd6-8c1e-d52b5b014ddf
    resourceVersion: "212142"
    uid: c201f9b0-cd23-49d0-b301-baa5128d181c
  spec:
    sourcePod: network-check-source-6f78d59f99-cm2k2
    targetEndpoint: a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T16:22:27Z"
      message: 'load-balancer-api-internal: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.53826ms
      message: 'load-balancer-api-internal: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:27Z"
    - latency: 7.279937ms
      message: 'load-balancer-api-internal: resolved host name a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:58:27Z"
    - latency: 16.210276ms
      message: 'load-balancer-api-internal: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:27Z"
    - latency: 6.663992ms
      message: 'load-balancer-api-internal: resolved host name a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:57:27Z"
    - latency: 19.028318ms
      message: 'load-balancer-api-internal: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:27Z"
    - latency: 50.428541ms
      message: 'load-balancer-api-internal: resolved host name a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:56:27Z"
    - latency: 13.847639ms
      message: 'load-balancer-api-internal: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:55:27Z"
    - latency: 6.336434ms
      message: 'load-balancer-api-internal: resolved host name a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:55:27Z"
    - latency: 18.634288ms
      message: 'load-balancer-api-internal: tcp connection to a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:54:27Z"
    - latency: 6.844492ms
      message: 'load-balancer-api-internal: resolved host name a95046cb55fe44b02b6e9ec48a053b09-444175b8eb8e2202.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:54:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T16:16:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-64-to-network-check-target-ip-10-0-129-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-64.ec2.internal
      uid: 43c100ce-ce0b-4fd6-8c1e-d52b5b014ddf
    resourceVersion: "214878"
    uid: 1036d672-6646-4219-9a51-c9c632fc5050
  spec:
    sourcePod: network-check-source-6f78d59f99-cm2k2
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T16:23:27Z"
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.342043ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:01:27Z"
    - latency: 909.802µs
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:00:27Z"
    - latency: 1.820203ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:59:27Z"
    - latency: 1.776959ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:27Z"
    - latency: 1.647381ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:27Z"
    - latency: 6.700751ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:27Z"
    - latency: 1.695466ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:55:27Z"
    - latency: 682.775µs
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:54:27Z"
    - latency: 2.169153ms
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:53:27Z"
    - latency: 631.279µs
      message: 'network-check-target-ip-10-0-129-130: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:52:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T16:16:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-64-to-network-check-target-ip-10-0-139-190
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-64.ec2.internal
      uid: 43c100ce-ce0b-4fd6-8c1e-d52b5b014ddf
    resourceVersion: "214876"
    uid: ed04805e-d81d-447c-99ac-23c166dd0b0c
  spec:
    sourcePod: network-check-source-6f78d59f99-cm2k2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T16:23:27Z"
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 13.878242ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:01:27Z"
    - latency: 1.906098ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:00:27Z"
    - latency: 2.123518ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:59:27Z"
    - latency: 625.059µs
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:27Z"
    - latency: 1.865311ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:27Z"
    - latency: 6.153392ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:27Z"
    - latency: 562.391µs
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:55:27Z"
    - latency: 1.992891ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:54:27Z"
    - latency: 1.962137ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:53:27Z"
    - latency: 2.016663ms
      message: 'network-check-target-ip-10-0-139-190: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:52:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T16:16:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-64-to-network-check-target-ip-10-0-143-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-64.ec2.internal
      uid: 43c100ce-ce0b-4fd6-8c1e-d52b5b014ddf
    resourceVersion: "214875"
    uid: b897aea5-e214-4e5c-971b-edddc71c169f
  spec:
    sourcePod: network-check-source-6f78d59f99-cm2k2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T16:23:27Z"
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 9.021374ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:01:27Z"
    - latency: 641.824µs
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T18:00:27Z"
    - latency: 438.114µs
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:59:27Z"
    - latency: 691.113µs
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:27Z"
    - latency: 477.526µs
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:27Z"
    - latency: 6.680801ms
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:27Z"
    - latency: 673.843µs
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:55:27Z"
    - latency: 727.169µs
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:54:27Z"
    - latency: 445.364µs
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:53:27Z"
    - latency: 679.229µs
      message: 'network-check-target-ip-10-0-143-64: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:52:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T16:16:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-64-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-64.ec2.internal
      uid: 43c100ce-ce0b-4fd6-8c1e-d52b5b014ddf
    resourceVersion: "212141"
    uid: 5703a917-cd03-4bc5-a623-af2043e128a9
  spec:
    sourcePod: network-check-source-6f78d59f99-cm2k2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T16:22:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.252788ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:58:27Z"
    - latency: 1.940178ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:58:27Z"
    - latency: 1.175377ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:57:27Z"
    - latency: 1.871966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:57:27Z"
    - latency: 9.093572ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:56:27Z"
    - latency: 7.855204ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:56:27Z"
    - latency: 2.237183ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:55:27Z"
    - latency: 1.742144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:55:27Z"
    - latency: 2.530573ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:54:27Z"
    - latency: 1.889744ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:54:27Z"
kind: List
metadata:
  resourceVersion: ""