apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:56:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-126-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-126.ec2.internal
      uid: 25162a7f-0089-457d-b5f3-aaba676da816
    resourceVersion: "23694"
    uid: 455bfc7a-4aa2-4822-8c7d-10f95330f09f
  spec:
    sourcePod: network-check-source-685456655f-dcncg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:03:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030874ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:17:47Z"
    - latency: 1.076342ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:16:47Z"
    - latency: 1.587252ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:15:47Z"
    - latency: 1.030873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:14:47Z"
    - latency: 952.102µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:13:47Z"
    - latency: 934.207µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:47Z"
    - latency: 1.135533ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:47Z"
    - latency: 1.001906ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:47Z"
    - latency: 1.280208ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:09:47Z"
    - latency: 952.6µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:08:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:56:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-126-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-126.ec2.internal
      uid: 25162a7f-0089-457d-b5f3-aaba676da816
    resourceVersion: "22175"
    uid: d9940ebb-c5a0-4a35-bef7-d4cf8ab76051
  spec:
    sourcePod: network-check-source-685456655f-dcncg
    targetEndpoint: a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:02:47Z"
      message: 'load-balancer-api-external: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.410909ms
      message: 'load-balancer-api-external: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:14:47Z"
    - latency: 9.301277ms
      message: 'load-balancer-api-external: resolved host name a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:14:47Z"
    - latency: 4.17653ms
      message: 'load-balancer-api-external: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:13:47Z"
    - latency: 8.830436ms
      message: 'load-balancer-api-external: resolved host name a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:13:47Z"
    - latency: 4.713892ms
      message: 'load-balancer-api-external: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:47Z"
    - latency: 8.270042ms
      message: 'load-balancer-api-external: resolved host name a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:12:47Z"
    - latency: 3.700207ms
      message: 'load-balancer-api-external: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:47Z"
    - latency: 8.770085ms
      message: 'load-balancer-api-external: resolved host name a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:11:47Z"
    - latency: 4.215501ms
      message: 'load-balancer-api-external: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:47Z"
    - latency: 8.116844ms
      message: 'load-balancer-api-external: resolved host name a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:10:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:56:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-126-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-126.ec2.internal
      uid: 25162a7f-0089-457d-b5f3-aaba676da816
    resourceVersion: "22174"
    uid: add95793-db64-4ef6-8da3-9bc16df508cc
  spec:
    sourcePod: network-check-source-685456655f-dcncg
    targetEndpoint: a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:02:47Z"
      message: 'load-balancer-api-internal: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.392719ms
      message: 'load-balancer-api-internal: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:14:47Z"
    - latency: 9.336185ms
      message: 'load-balancer-api-internal: resolved host name a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:14:47Z"
    - latency: 4.509694ms
      message: 'load-balancer-api-internal: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:13:47Z"
    - latency: 8.909983ms
      message: 'load-balancer-api-internal: resolved host name a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:13:47Z"
    - latency: 4.695789ms
      message: 'load-balancer-api-internal: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:47Z"
    - latency: 8.303974ms
      message: 'load-balancer-api-internal: resolved host name a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:12:47Z"
    - latency: 3.662353ms
      message: 'load-balancer-api-internal: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:47Z"
    - latency: 8.837493ms
      message: 'load-balancer-api-internal: resolved host name a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:11:47Z"
    - latency: 4.198635ms
      message: 'load-balancer-api-internal: tcp connection to a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:47Z"
    - latency: 8.086676ms
      message: 'load-balancer-api-internal: resolved host name a6c92cc91589b4fe8a05fc287aab7d83-7f3274dd0dbaa56c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:10:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:56:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-129-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-126.ec2.internal
      uid: 25162a7f-0089-457d-b5f3-aaba676da816
    resourceVersion: "23692"
    uid: 406e414b-7b93-4a15-a012-7d17b1e4eea3
  spec:
    sourcePod: network-check-source-685456655f-dcncg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:03:47Z"
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.56739ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:17:47Z"
    - latency: 2.312808ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:16:47Z"
    - latency: 2.757594ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:15:47Z"
    - latency: 2.672465ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:14:47Z"
    - latency: 2.523466ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:13:47Z"
    - latency: 2.301786ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:47Z"
    - latency: 2.350346ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:47Z"
    - latency: 2.660178ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:47Z"
    - latency: 2.231714ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:09:47Z"
    - latency: 2.505371ms
      message: 'network-check-target-ip-10-0-129-205: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:08:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:56:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-136-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-126.ec2.internal
      uid: 25162a7f-0089-457d-b5f3-aaba676da816
    resourceVersion: "23691"
    uid: a19fdedd-3c8c-4049-83c1-3f6321efdd99
  spec:
    sourcePod: network-check-source-685456655f-dcncg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:03:47Z"
      message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.700031ms
      message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:17:47Z"
    - latency: 1.414484ms
      message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:16:47Z"
    - latency: 1.747326ms
      message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:15:47Z"
    - latency: 914.187µs
      message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:14:47Z"
    - latency: 1.464334ms
      message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:13:47Z"
    - latency: 939.033µs
      message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:47Z"
    - latency: 971.604µs
      message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:47Z"
    - latency: 1.391308ms
      message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:47Z"
    - latency: 907.743µs
      message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:09:47Z"
    - latency: 972.448µs
      message: 'network-check-target-ip-10-0-136-126: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:08:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:56:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-126-to-network-check-target-ip-10-0-138-224
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-126.ec2.internal
      uid: 25162a7f-0089-457d-b5f3-aaba676da816
    resourceVersion: "23693"
    uid: 8c3d6d32-a1f0-443d-abcf-aa689eb8e0be
  spec:
    sourcePod: network-check-source-685456655f-dcncg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:03:47Z"
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.617936ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:17:47Z"
    - latency: 2.364953ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:16:47Z"
    - latency: 2.529926ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:15:47Z"
    - latency: 2.390364ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:14:47Z"
    - latency: 5.943051ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:13:47Z"
    - latency: 2.354363ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:47Z"
    - latency: 2.229155ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:47Z"
    - latency: 2.163294ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:47Z"
    - latency: 2.282453ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:09:47Z"
    - latency: 2.503624ms
      message: 'network-check-target-ip-10-0-138-224: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:08:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T20:56:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-126-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-126.ec2.internal
      uid: 25162a7f-0089-457d-b5f3-aaba676da816
    resourceVersion: "22173"
    uid: b98a999c-7016-48ba-91ed-68a75ae90d54
  spec:
    sourcePod: network-check-source-685456655f-dcncg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T21:02:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.044349ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:14:47Z"
    - latency: 2.819905ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:14:47Z"
    - latency: 1.152983ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:13:47Z"
    - latency: 1.867937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:13:47Z"
    - latency: 1.137726ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:12:47Z"
    - latency: 1.876783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:12:47Z"
    - latency: 995.673µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:11:47Z"
    - latency: 1.956952ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:11:47Z"
    - latency: 1.311292ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T21:10:47Z"
    - latency: 1.781494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T21:10:47Z"
kind: List
metadata:
  resourceVersion: ""