apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 6f5ddca7-eae0-49ed-82d9-05a376ad386f
    resourceVersion: "55754"
    uid: fd591589-3e10-450b-a8af-dbb3a33a980f
  spec:
    sourcePod: network-check-source-989f8b8dc-79mnm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:52:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.110068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:20:20Z"
    - latency: 900.911µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:19:20Z"
    - latency: 989.008µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:18:20Z"
    - latency: 1.061581ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:17:20Z"
    - latency: 1.100953ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:16:20Z"
    - latency: 1.462843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:15:20Z"
    - latency: 938.243µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:14:20Z"
    - latency: 942.921µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:13:20Z"
    - latency: 955.624µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:12:20Z"
    - latency: 906.426µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:11:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 6f5ddca7-eae0-49ed-82d9-05a376ad386f
    resourceVersion: "56691"
    uid: 3d45d878-c150-4500-a08b-959772b2b550
  spec:
    sourcePod: network-check-source-989f8b8dc-79mnm
    targetEndpoint: aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:51:20Z"
      message: 'load-balancer-api-external: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.783649ms
      message: 'load-balancer-api-external: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:21:20Z"
    - latency: 6.487779ms
      message: 'load-balancer-api-external: resolved host name aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:21:20Z"
    - latency: 4.864742ms
      message: 'load-balancer-api-external: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:20:20Z"
    - latency: 7.786831ms
      message: 'load-balancer-api-external: resolved host name aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:20:20Z"
    - latency: 4.517106ms
      message: 'load-balancer-api-external: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:19:20Z"
    - latency: 7.130284ms
      message: 'load-balancer-api-external: resolved host name aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:19:20Z"
    - latency: 4.428253ms
      message: 'load-balancer-api-external: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:18:20Z"
    - latency: 6.990546ms
      message: 'load-balancer-api-external: resolved host name aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:18:20Z"
    - latency: 3.940117ms
      message: 'load-balancer-api-external: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:17:20Z"
    - latency: 6.738356ms
      message: 'load-balancer-api-external: resolved host name aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:17:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 6f5ddca7-eae0-49ed-82d9-05a376ad386f
    resourceVersion: "56692"
    uid: 0a8bf209-ade6-4eaf-a1fb-a42791e7cc07
  spec:
    sourcePod: network-check-source-989f8b8dc-79mnm
    targetEndpoint: aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:51:20Z"
      message: 'load-balancer-api-internal: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.762427ms
      message: 'load-balancer-api-internal: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:21:20Z"
    - latency: 6.512141ms
      message: 'load-balancer-api-internal: resolved host name aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:21:20Z"
    - latency: 4.894957ms
      message: 'load-balancer-api-internal: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:20:20Z"
    - latency: 7.822753ms
      message: 'load-balancer-api-internal: resolved host name aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:20:20Z"
    - latency: 4.093205ms
      message: 'load-balancer-api-internal: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:19:20Z"
    - latency: 7.11978ms
      message: 'load-balancer-api-internal: resolved host name aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:19:20Z"
    - latency: 3.822155ms
      message: 'load-balancer-api-internal: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:18:20Z"
    - latency: 6.966767ms
      message: 'load-balancer-api-internal: resolved host name aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:18:20Z"
    - latency: 5.451651ms
      message: 'load-balancer-api-internal: tcp connection to aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:17:20Z"
    - latency: 6.754077ms
      message: 'load-balancer-api-internal: resolved host name aaf29db1a885742ce90b6f8c3d6ef87d-ab90921e603a0704.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:17:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-network-check-target-ip-10-0-130-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 6f5ddca7-eae0-49ed-82d9-05a376ad386f
    resourceVersion: "55751"
    uid: db2a23dd-9965-4433-b71e-ef59ef8dbac9
  spec:
    sourcePod: network-check-source-989f8b8dc-79mnm
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:52:20Z"
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.099µs
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:20:20Z"
    - latency: 882.949µs
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:19:20Z"
    - latency: 1.207888ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:18:20Z"
    - latency: 937.405µs
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:17:20Z"
    - latency: 1.663608ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:16:20Z"
    - latency: 933.914µs
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:15:20Z"
    - latency: 1.407567ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:14:20Z"
    - latency: 1.11899ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:13:20Z"
    - latency: 1.4258ms
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:12:20Z"
    - latency: 888.955µs
      message: 'network-check-target-ip-10-0-130-182: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:11:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-network-check-target-ip-10-0-131-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 6f5ddca7-eae0-49ed-82d9-05a376ad386f
    resourceVersion: "55752"
    uid: d2c3d3f1-82c1-4ec1-9169-1c954624d7a8
  spec:
    sourcePod: network-check-source-989f8b8dc-79mnm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:52:20Z"
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.304114ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:20:20Z"
    - latency: 2.273977ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:19:20Z"
    - latency: 2.294774ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:18:20Z"
    - latency: 2.200684ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:17:20Z"
    - latency: 2.047844ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:16:20Z"
    - latency: 2.36731ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:15:20Z"
    - latency: 2.239746ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:14:20Z"
    - latency: 2.239795ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:13:20Z"
    - latency: 2.129006ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:12:20Z"
    - latency: 2.212932ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:11:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-network-check-target-ip-10-0-142-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 6f5ddca7-eae0-49ed-82d9-05a376ad386f
    resourceVersion: "55753"
    uid: dd2f04a8-d428-4949-8c45-3db212977e65
  spec:
    sourcePod: network-check-source-989f8b8dc-79mnm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:52:20Z"
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.476644ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:20:20Z"
    - latency: 2.30582ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:19:20Z"
    - latency: 1.99058ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:18:20Z"
    - latency: 2.263799ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:17:20Z"
    - latency: 2.175469ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:16:20Z"
    - latency: 2.345466ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:15:20Z"
    - latency: 2.507058ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:14:20Z"
    - latency: 2.263019ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:13:20Z"
    - latency: 2.179258ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:12:20Z"
    - latency: 1.911491ms
      message: 'network-check-target-ip-10-0-142-97: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:11:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T13:45:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-182-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-182.ec2.internal
      uid: 6f5ddca7-eae0-49ed-82d9-05a376ad386f
    resourceVersion: "56690"
    uid: 9d23afdf-f2a2-4f15-97dc-18b80375f966
  spec:
    sourcePod: network-check-source-989f8b8dc-79mnm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T13:51:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.011µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:21:20Z"
    - latency: 1.562974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:21:20Z"
    - latency: 947.404µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:20:20Z"
    - latency: 1.734028ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:20:20Z"
    - latency: 802.108µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:19:20Z"
    - latency: 1.525452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:19:20Z"
    - latency: 980.721µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:18:20Z"
    - latency: 1.880786ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:18:20Z"
    - latency: 1.112751ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T14:17:20Z"
    - latency: 1.715965ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T14:17:20Z"
kind: List
metadata:
  resourceVersion: ""