apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: 59b5a2d6-d4ec-4cc5-9a67-1f3f123dc37d
    resourceVersion: "49180"
    uid: d8f605e3-c4bd-4207-ac24-79c966211257
  spec:
    sourcePod: network-check-source-989f8b8dc-d5shj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:37:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.409213ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:36Z"
    - latency: 884.175µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:37Z"
    - latency: 950.455µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:37Z"
    - latency: 893.592µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:37Z"
    - latency: 1.171558ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:36Z"
    - latency: 1.08143ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:36Z"
    - latency: 1.074941ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:36Z"
    - latency: 1.09534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:37Z"
    - latency: 1.329239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:57:37Z"
    - latency: 982.438µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:56:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: 59b5a2d6-d4ec-4cc5-9a67-1f3f123dc37d
    resourceVersion: "49999"
    uid: ac51b5ab-cbcb-422b-a8b4-11342d612f09
  spec:
    sourcePod: network-check-source-989f8b8dc-d5shj
    targetEndpoint: af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:36:37Z"
      message: 'load-balancer-api-external: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.015956ms
      message: 'load-balancer-api-external: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:37Z"
    - latency: 7.154786ms
      message: 'load-balancer-api-external: resolved host name af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:36Z"
    - latency: 3.983383ms
      message: 'load-balancer-api-external: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:37Z"
    - latency: 7.129682ms
      message: 'load-balancer-api-external: resolved host name af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:36Z"
    - latency: 5.389152ms
      message: 'load-balancer-api-external: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:37Z"
    - latency: 6.817218ms
      message: 'load-balancer-api-external: resolved host name af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:37Z"
    - latency: 6.389348ms
      message: 'load-balancer-api-external: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:37Z"
    - latency: 7.182437ms
      message: 'load-balancer-api-external: resolved host name af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:03:37Z"
    - latency: 5.636569ms
      message: 'load-balancer-api-external: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:37Z"
    - latency: 6.79608ms
      message: 'load-balancer-api-external: resolved host name af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:02:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: 59b5a2d6-d4ec-4cc5-9a67-1f3f123dc37d
    resourceVersion: "50000"
    uid: d750b5ea-7a42-42ed-b014-65a30fc40318
  spec:
    sourcePod: network-check-source-989f8b8dc-d5shj
    targetEndpoint: af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:36:37Z"
      message: 'load-balancer-api-internal: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.995796ms
      message: 'load-balancer-api-internal: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:37Z"
    - latency: 7.245382ms
      message: 'load-balancer-api-internal: resolved host name af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:36Z"
    - latency: 4.032121ms
      message: 'load-balancer-api-internal: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:37Z"
    - latency: 7.090886ms
      message: 'load-balancer-api-internal: resolved host name af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:36Z"
    - latency: 3.740141ms
      message: 'load-balancer-api-internal: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:37Z"
    - latency: 6.896477ms
      message: 'load-balancer-api-internal: resolved host name af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:37Z"
    - latency: 6.39691ms
      message: 'load-balancer-api-internal: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:37Z"
    - latency: 7.131322ms
      message: 'load-balancer-api-internal: resolved host name af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:03:37Z"
    - latency: 4.428675ms
      message: 'load-balancer-api-internal: tcp connection to af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:37Z"
    - latency: 6.885492ms
      message: 'load-balancer-api-internal: resolved host name af5fb07a8ae774563ae27fb56f53ed73-70a139c4bfb6e956.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:02:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-network-check-target-ip-10-0-135-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: 59b5a2d6-d4ec-4cc5-9a67-1f3f123dc37d
    resourceVersion: "49178"
    uid: c949bcad-94f9-4796-a0fc-39ef5cdcf264
  spec:
    sourcePod: network-check-source-989f8b8dc-d5shj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:37:37Z"
      message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.532454ms
      message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:36Z"
    - latency: 2.285946ms
      message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:37Z"
    - latency: 2.219828ms
      message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:37Z"
    - latency: 1.904733ms
      message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:37Z"
    - latency: 2.337057ms
      message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:36Z"
    - latency: 2.118577ms
      message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:36Z"
    - latency: 2.301656ms
      message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:36Z"
    - latency: 1.961638ms
      message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:37Z"
    - latency: 1.909621ms
      message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:57:37Z"
    - latency: 2.112055ms
      message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:56:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-network-check-target-ip-10-0-136-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: 59b5a2d6-d4ec-4cc5-9a67-1f3f123dc37d
    resourceVersion: "49179"
    uid: b1a9d9a8-5a67-4635-b408-ffb7cd9205ea
  spec:
    sourcePod: network-check-source-989f8b8dc-d5shj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:37:37Z"
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.54364ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:36Z"
    - latency: 2.333692ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:37Z"
    - latency: 2.260424ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:37Z"
    - latency: 2.156509ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:37Z"
    - latency: 2.299531ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:36Z"
    - latency: 2.108042ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:36Z"
    - latency: 2.233259ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:36Z"
    - latency: 2.311572ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:37Z"
    - latency: 2.4356ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:57:37Z"
    - latency: 2.301794ms
      message: 'network-check-target-ip-10-0-136-156: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:56:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-network-check-target-ip-10-0-143-100
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: 59b5a2d6-d4ec-4cc5-9a67-1f3f123dc37d
    resourceVersion: "49177"
    uid: 91f5ade4-9bf0-4f2e-9cc6-38fac65b0e1e
  spec:
    sourcePod: network-check-source-989f8b8dc-d5shj
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:37:37Z"
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.009516ms
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:36Z"
    - latency: 880.496µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:37Z"
    - latency: 923.627µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:37Z"
    - latency: 1.536315ms
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:37Z"
    - latency: 934.46µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:01:36Z"
    - latency: 817.581µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:00:37Z"
    - latency: 1.307377ms
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:59:36Z"
    - latency: 933.452µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:58:37Z"
    - latency: 1.186686ms
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:57:37Z"
    - latency: 897.88µs
      message: 'network-check-target-ip-10-0-143-100: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:56:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:30:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-100-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-100.ec2.internal
      uid: 59b5a2d6-d4ec-4cc5-9a67-1f3f123dc37d
    resourceVersion: "49998"
    uid: e949f146-b6c5-4280-b56f-0940f586d9cc
  spec:
    sourcePod: network-check-source-989f8b8dc-d5shj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:36:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.04417ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:37Z"
    - latency: 1.916082ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:06:36Z"
    - latency: 1.03052ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:37Z"
    - latency: 1.919542ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:05:36Z"
    - latency: 806.82µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:37Z"
    - latency: 1.773838ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:04:37Z"
    - latency: 917.712µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:03:37Z"
    - latency: 1.863856ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:03:37Z"
    - latency: 1.171533ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:02:37Z"
    - latency: 1.788213ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:02:37Z"
kind: List
metadata:
  resourceVersion: ""