apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:40:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-71-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-71.ec2.internal
      uid: 2a460f6a-a2e3-49a7-99f8-e13bf751113f
    resourceVersion: "39782"
    uid: 1e2d4c87-e8c7-44cb-adcf-b7c662663e17
  spec:
    sourcePod: network-check-source-7cbc45fddc-dp2xf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:47:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.273437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:42Z"
    - latency: 905.909µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:42Z"
    - latency: 977.995µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:42Z"
    - latency: 877.259µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:42Z"
    - latency: 1.181697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:42Z"
    - latency: 725.55µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:42Z"
    - latency: 1.297876ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:42Z"
    - latency: 1.205105ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:42Z"
    - latency: 1.156161ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:42Z"
    - latency: 1.111729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:40:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-71-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-71.ec2.internal
      uid: 2a460f6a-a2e3-49a7-99f8-e13bf751113f
    resourceVersion: "39356"
    uid: f79b701a-3858-4552-a7aa-7afbb82489ab
  spec:
    sourcePod: network-check-source-7cbc45fddc-dp2xf
    targetEndpoint: a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:46:42Z"
      message: 'load-balancer-api-external: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.388362ms
      message: 'load-balancer-api-external: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:42Z"
    - latency: 8.196241ms
      message: 'load-balancer-api-external: resolved host name a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:28:42Z"
    - latency: 3.996291ms
      message: 'load-balancer-api-external: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:42Z"
    - latency: 17.719014ms
      message: 'load-balancer-api-external: resolved host name a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:27:42Z"
    - latency: 3.274828ms
      message: 'load-balancer-api-external: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:42Z"
    - latency: 7.803754ms
      message: 'load-balancer-api-external: resolved host name a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:26:42Z"
    - latency: 6.493572ms
      message: 'load-balancer-api-external: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:42Z"
    - latency: 8.360126ms
      message: 'load-balancer-api-external: resolved host name a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:25:42Z"
    - latency: 5.161252ms
      message: 'load-balancer-api-external: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:42Z"
    - latency: 9.449152ms
      message: 'load-balancer-api-external: resolved host name a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:24:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:40:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-71-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-71.ec2.internal
      uid: 2a460f6a-a2e3-49a7-99f8-e13bf751113f
    resourceVersion: "39357"
    uid: 2bcad9ac-b454-48d1-b868-d9400c05f595
  spec:
    sourcePod: network-check-source-7cbc45fddc-dp2xf
    targetEndpoint: a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:46:42Z"
      message: 'load-balancer-api-internal: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.344881ms
      message: 'load-balancer-api-internal: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:42Z"
    - latency: 8.227545ms
      message: 'load-balancer-api-internal: resolved host name a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:28:42Z"
    - latency: 3.9769ms
      message: 'load-balancer-api-internal: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:42Z"
    - latency: 17.740803ms
      message: 'load-balancer-api-internal: resolved host name a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:27:42Z"
    - latency: 6.672144ms
      message: 'load-balancer-api-internal: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:42Z"
    - latency: 7.871121ms
      message: 'load-balancer-api-internal: resolved host name a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:26:42Z"
    - latency: 6.51363ms
      message: 'load-balancer-api-internal: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:42Z"
    - latency: 8.448857ms
      message: 'load-balancer-api-internal: resolved host name a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:25:42Z"
    - latency: 5.451042ms
      message: 'load-balancer-api-internal: tcp connection to a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:42Z"
    - latency: 9.399814ms
      message: 'load-balancer-api-internal: resolved host name a0eac2ae9bbb8473a8af7f99af94f808-2690adc281dd50e8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:24:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:40:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-71-to-network-check-target-ip-10-0-133-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-71.ec2.internal
      uid: 2a460f6a-a2e3-49a7-99f8-e13bf751113f
    resourceVersion: "39781"
    uid: 31c9a701-7111-495e-83ab-49eff6a20cf4
  spec:
    sourcePod: network-check-source-7cbc45fddc-dp2xf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:47:42Z"
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.654749ms
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:42Z"
    - latency: 2.460608ms
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:42Z"
    - latency: 2.527785ms
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:42Z"
    - latency: 2.345776ms
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:42Z"
    - latency: 2.289889ms
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:42Z"
    - latency: 1.761034ms
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:42Z"
    - latency: 2.124597ms
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:42Z"
    - latency: 3.140462ms
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:42Z"
    - latency: 2.202573ms
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:42Z"
    - latency: 2.395196ms
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:40:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-71-to-network-check-target-ip-10-0-133-71
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-71.ec2.internal
      uid: 2a460f6a-a2e3-49a7-99f8-e13bf751113f
    resourceVersion: "39779"
    uid: 91fc3ee7-e4a2-4665-a299-918733352210
  spec:
    sourcePod: network-check-source-7cbc45fddc-dp2xf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:47:42Z"
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.553423ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:42Z"
    - latency: 840.218µs
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:42Z"
    - latency: 907.384µs
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:42Z"
    - latency: 907.215µs
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:42Z"
    - latency: 889.482µs
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:42Z"
    - latency: 735.387µs
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:42Z"
    - latency: 676.585µs
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:42Z"
    - latency: 1.614843ms
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:42Z"
    - latency: 857.91µs
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:42Z"
    - latency: 734.087µs
      message: 'network-check-target-ip-10-0-133-71: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:40:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-71-to-network-check-target-ip-10-0-138-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-71.ec2.internal
      uid: 2a460f6a-a2e3-49a7-99f8-e13bf751113f
    resourceVersion: "39780"
    uid: d810aa54-02fc-4870-8eed-1ae7e2c37962
  spec:
    sourcePod: network-check-source-7cbc45fddc-dp2xf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:47:42Z"
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.24665ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:29:42Z"
    - latency: 2.46679ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:42Z"
    - latency: 2.468394ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:42Z"
    - latency: 2.37993ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:42Z"
    - latency: 2.495647ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:42Z"
    - latency: 2.081576ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:42Z"
    - latency: 2.254919ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:23:42Z"
    - latency: 3.74369ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:22:42Z"
    - latency: 2.306013ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:21:42Z"
    - latency: 2.503995ms
      message: 'network-check-target-ip-10-0-138-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:20:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T17:40:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-71-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-71.ec2.internal
      uid: 2a460f6a-a2e3-49a7-99f8-e13bf751113f
    resourceVersion: "39355"
    uid: d584c7bc-b05e-41a8-a65f-915034030212
  spec:
    sourcePod: network-check-source-7cbc45fddc-dp2xf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T17:46:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 701.006µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:28:42Z"
    - latency: 1.678514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:28:42Z"
    - latency: 1.063644ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:27:42Z"
    - latency: 1.62829ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:27:42Z"
    - latency: 1.217569ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:26:42Z"
    - latency: 1.617824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:26:42Z"
    - latency: 1.372457ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:25:42Z"
    - latency: 1.89711ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:25:42Z"
    - latency: 840.988µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T18:24:42Z"
    - latency: 1.650594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T18:24:42Z"
kind: List
metadata:
  resourceVersion: ""