apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T11:57:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-207-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-207.ec2.internal
      uid: de4c0577-c74a-467c-821e-37ed6d86db45
    resourceVersion: "54666"
    uid: 6b76c4b9-60ae-4fe7-9891-d15b7225b3f1
  spec:
    sourcePod: network-check-source-989f8b8dc-768g2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T12:04:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.269207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:32:50Z"
    - latency: 1.826331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:31:50Z"
    - latency: 1.260647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:30:50Z"
    - latency: 1.306944ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:29:50Z"
    - latency: 1.179491ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:28:50Z"
    - latency: 907.832µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:27:50Z"
    - latency: 1.474753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:26:50Z"
    - latency: 932.01µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:25:50Z"
    - latency: 1.064256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:24:50Z"
    - latency: 1.414908ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:23:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T11:57:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-207-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-207.ec2.internal
      uid: de4c0577-c74a-467c-821e-37ed6d86db45
    resourceVersion: "55639"
    uid: a5dbf316-dce4-4fab-9939-8ed09a2e0891
  spec:
    sourcePod: network-check-source-989f8b8dc-768g2
    targetEndpoint: a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T12:03:50Z"
      message: 'load-balancer-api-external: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.69152ms
      message: 'load-balancer-api-external: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:33:50Z"
    - latency: 9.99133ms
      message: 'load-balancer-api-external: resolved host name a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:33:50Z"
    - latency: 5.911314ms
      message: 'load-balancer-api-external: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:32:50Z"
    - latency: 8.877942ms
      message: 'load-balancer-api-external: resolved host name a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:32:50Z"
    - latency: 5.636019ms
      message: 'load-balancer-api-external: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:31:50Z"
    - latency: 8.581624ms
      message: 'load-balancer-api-external: resolved host name a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:31:50Z"
    - latency: 4.771972ms
      message: 'load-balancer-api-external: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:30:50Z"
    - latency: 8.736594ms
      message: 'load-balancer-api-external: resolved host name a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:30:50Z"
    - latency: 4.957084ms
      message: 'load-balancer-api-external: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:29:50Z"
    - latency: 8.846754ms
      message: 'load-balancer-api-external: resolved host name a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:29:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T11:57:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-207-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-207.ec2.internal
      uid: de4c0577-c74a-467c-821e-37ed6d86db45
    resourceVersion: "55640"
    uid: 9a2f6588-5804-45c2-bc72-844d2b042100
  spec:
    sourcePod: network-check-source-989f8b8dc-768g2
    targetEndpoint: a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T12:03:50Z"
      message: 'load-balancer-api-internal: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.752161ms
      message: 'load-balancer-api-internal: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:33:50Z"
    - latency: 10.079628ms
      message: 'load-balancer-api-internal: resolved host name a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:33:50Z"
    - latency: 6.17855ms
      message: 'load-balancer-api-internal: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:32:50Z"
    - latency: 8.80933ms
      message: 'load-balancer-api-internal: resolved host name a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:32:50Z"
    - latency: 5.56894ms
      message: 'load-balancer-api-internal: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:31:50Z"
    - latency: 8.55436ms
      message: 'load-balancer-api-internal: resolved host name a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:31:50Z"
    - latency: 4.118577ms
      message: 'load-balancer-api-internal: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:30:50Z"
    - latency: 8.615285ms
      message: 'load-balancer-api-internal: resolved host name a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:30:50Z"
    - latency: 4.105993ms
      message: 'load-balancer-api-internal: tcp connection to a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:29:50Z"
    - latency: 8.99045ms
      message: 'load-balancer-api-internal: resolved host name a691aed2c7ad74aafac5f41a92ac6c32-98702ab69bb20dbc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:29:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T11:57:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-207-to-network-check-target-ip-10-0-136-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-207.ec2.internal
      uid: de4c0577-c74a-467c-821e-37ed6d86db45
    resourceVersion: "54664"
    uid: de6b9cf8-0746-4042-b0bf-1557725948f5
  spec:
    sourcePod: network-check-source-989f8b8dc-768g2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T12:04:50Z"
      message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.313778ms
      message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:32:50Z"
    - latency: 2.626726ms
      message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:31:50Z"
    - latency: 2.313929ms
      message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:30:50Z"
    - latency: 2.363932ms
      message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:29:50Z"
    - latency: 2.267697ms
      message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:28:50Z"
    - latency: 1.879124ms
      message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:27:50Z"
    - latency: 2.404995ms
      message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:26:50Z"
    - latency: 2.364974ms
      message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:25:50Z"
    - latency: 2.325728ms
      message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:24:50Z"
    - latency: 2.44285ms
      message: 'network-check-target-ip-10-0-136-198: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:23:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T11:57:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-207-to-network-check-target-ip-10-0-142-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-207.ec2.internal
      uid: de4c0577-c74a-467c-821e-37ed6d86db45
    resourceVersion: "54663"
    uid: b6d1948e-16f1-430c-8a9a-920a09692e7b
  spec:
    sourcePod: network-check-source-989f8b8dc-768g2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T12:04:50Z"
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 934.324µs
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:32:50Z"
    - latency: 1.064323ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:31:50Z"
    - latency: 991.833µs
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:30:50Z"
    - latency: 825.079µs
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:29:50Z"
    - latency: 988.284µs
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:28:50Z"
    - latency: 877.774µs
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:27:50Z"
    - latency: 931.899µs
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:26:50Z"
    - latency: 1.025662ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:25:50Z"
    - latency: 940.557µs
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:24:50Z"
    - latency: 1.399645ms
      message: 'network-check-target-ip-10-0-142-207: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:23:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T11:57:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-207-to-network-check-target-ip-10-0-143-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-207.ec2.internal
      uid: de4c0577-c74a-467c-821e-37ed6d86db45
    resourceVersion: "54665"
    uid: 5c1fc9d4-d4c8-4037-9db8-00f2c9b9631c
  spec:
    sourcePod: network-check-source-989f8b8dc-768g2
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T12:04:50Z"
      message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.022833ms
      message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:32:50Z"
    - latency: 1.965177ms
      message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:31:50Z"
    - latency: 1.894062ms
      message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:30:50Z"
    - latency: 2.027664ms
      message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:29:50Z"
    - latency: 1.935317ms
      message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:28:50Z"
    - latency: 1.940325ms
      message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:27:50Z"
    - latency: 2.044251ms
      message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:26:50Z"
    - latency: 2.007848ms
      message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:25:50Z"
    - latency: 1.954778ms
      message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:24:50Z"
    - latency: 2.024134ms
      message: 'network-check-target-ip-10-0-143-202: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:23:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-05T11:57:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-207-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-207.ec2.internal
      uid: de4c0577-c74a-467c-821e-37ed6d86db45
    resourceVersion: "55637"
    uid: 511f2c4c-d664-4b7d-a058-b2f575dd4f0f
  spec:
    sourcePod: network-check-source-989f8b8dc-768g2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-05T12:03:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 974.418µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:33:50Z"
    - latency: 1.95062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:33:50Z"
    - latency: 1.230995ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:32:50Z"
    - latency: 2.030089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:32:50Z"
    - latency: 899.76µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:31:50Z"
    - latency: 2.486208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:31:50Z"
    - latency: 718.71µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:30:50Z"
    - latency: 2.175699ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:30:50Z"
    - latency: 1.147994ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-05T12:29:50Z"
    - latency: 1.777464ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-05T12:29:50Z"
kind: List
metadata:
  resourceVersion: ""