apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T15:17:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-176-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-176.ec2.internal
      uid: 1b830d6f-a247-4c16-a3a1-b542ee500867
    resourceVersion: "54721"
    uid: 8b7fcc0c-154f-401c-a144-8dfec8b426eb
  spec:
    sourcePod: network-check-source-989f8b8dc-fm5jm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T15:24:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.099µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:52:31Z"
    - latency: 1.155017ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:51:31Z"
    - latency: 1.125102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:50:31Z"
    - latency: 908.276µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:49:31Z"
    - latency: 3.516419ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:48:31Z"
    - latency: 1.015901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:47:31Z"
    - latency: 1.784083ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:46:31Z"
    - latency: 4.833813ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:45:31Z"
    - latency: 1.12768ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:44:31Z"
    - latency: 1.093332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:43:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T15:17:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-176-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-176.ec2.internal
      uid: 1b830d6f-a247-4c16-a3a1-b542ee500867
    resourceVersion: "55587"
    uid: 134d8371-623f-4403-aab6-998a09180375
  spec:
    sourcePod: network-check-source-989f8b8dc-fm5jm
    targetEndpoint: aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T15:23:31Z"
      message: 'load-balancer-api-external: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.148334ms
      message: 'load-balancer-api-external: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:53:31Z"
    - latency: 7.303711ms
      message: 'load-balancer-api-external: resolved host name aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:53:31Z"
    - latency: 3.99172ms
      message: 'load-balancer-api-external: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:52:31Z"
    - latency: 7.0862ms
      message: 'load-balancer-api-external: resolved host name aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:52:31Z"
    - latency: 5.658747ms
      message: 'load-balancer-api-external: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:51:31Z"
    - latency: 7.452876ms
      message: 'load-balancer-api-external: resolved host name aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:51:31Z"
    - latency: 4.285766ms
      message: 'load-balancer-api-external: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:50:31Z"
    - latency: 7.439619ms
      message: 'load-balancer-api-external: resolved host name aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:50:31Z"
    - latency: 5.670491ms
      message: 'load-balancer-api-external: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:49:31Z"
    - latency: 6.96794ms
      message: 'load-balancer-api-external: resolved host name aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:49:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T15:17:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-176-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-176.ec2.internal
      uid: 1b830d6f-a247-4c16-a3a1-b542ee500867
    resourceVersion: "55586"
    uid: 02408442-84fe-42be-98d8-1e95a686306b
  spec:
    sourcePod: network-check-source-989f8b8dc-fm5jm
    targetEndpoint: aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T15:23:31Z"
      message: 'load-balancer-api-internal: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.117609ms
      message: 'load-balancer-api-internal: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:53:31Z"
    - latency: 7.40536ms
      message: 'load-balancer-api-internal: resolved host name aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:53:31Z"
    - latency: 4.986507ms
      message: 'load-balancer-api-internal: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:52:31Z"
    - latency: 7.055912ms
      message: 'load-balancer-api-internal: resolved host name aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:52:31Z"
    - latency: 5.625422ms
      message: 'load-balancer-api-internal: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:51:31Z"
    - latency: 7.50166ms
      message: 'load-balancer-api-internal: resolved host name aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:51:31Z"
    - latency: 4.718421ms
      message: 'load-balancer-api-internal: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:50:31Z"
    - latency: 7.552094ms
      message: 'load-balancer-api-internal: resolved host name aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:50:31Z"
    - latency: 5.593194ms
      message: 'load-balancer-api-internal: tcp connection to aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:49:31Z"
    - latency: 7.081051ms
      message: 'load-balancer-api-internal: resolved host name aa99f2a6418444f01ac61fee6b06c4c5-0cb87fd65383ee35.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:49:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T15:17:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-176-to-network-check-target-ip-10-0-138-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-176.ec2.internal
      uid: 1b830d6f-a247-4c16-a3a1-b542ee500867
    resourceVersion: "54718"
    uid: 931667cb-395a-43cf-bae4-9d3baf87c73f
  spec:
    sourcePod: network-check-source-989f8b8dc-fm5jm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T15:24:31Z"
      message: 'network-check-target-ip-10-0-138-243: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.262508ms
      message: 'network-check-target-ip-10-0-138-243: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:52:31Z"
    - latency: 2.905421ms
      message: 'network-check-target-ip-10-0-138-243: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:51:31Z"
    - latency: 2.587207ms
      message: 'network-check-target-ip-10-0-138-243: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:50:31Z"
    - latency: 2.288431ms
      message: 'network-check-target-ip-10-0-138-243: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:49:31Z"
    - latency: 2.752749ms
      message: 'network-check-target-ip-10-0-138-243: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:48:31Z"
    - latency: 2.36032ms
      message: 'network-check-target-ip-10-0-138-243: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:47:31Z"
    - latency: 2.536096ms
      message: 'network-check-target-ip-10-0-138-243: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:46:31Z"
    - latency: 2.545284ms
      message: 'network-check-target-ip-10-0-138-243: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:45:31Z"
    - latency: 2.324445ms
      message: 'network-check-target-ip-10-0-138-243: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:44:31Z"
    - latency: 2.265044ms
      message: 'network-check-target-ip-10-0-138-243: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:43:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T15:17:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-176-to-network-check-target-ip-10-0-142-176
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-176.ec2.internal
      uid: 1b830d6f-a247-4c16-a3a1-b542ee500867
    resourceVersion: "54719"
    uid: 4d3d505a-5321-47fd-8b9a-127f7542c3ba
  spec:
    sourcePod: network-check-source-989f8b8dc-fm5jm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T15:24:31Z"
      message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.255628ms
      message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:52:31Z"
    - latency: 1.334845ms
      message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:51:31Z"
    - latency: 890.929µs
      message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:50:31Z"
    - latency: 908.745µs
      message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:49:31Z"
    - latency: 1.177425ms
      message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:48:31Z"
    - latency: 962.188µs
      message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:47:31Z"
    - latency: 1.265286ms
      message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:46:31Z"
    - latency: 4.962732ms
      message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:45:31Z"
    - latency: 743.087µs
      message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:44:31Z"
    - latency: 860.527µs
      message: 'network-check-target-ip-10-0-142-176: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:43:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T15:17:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-176-to-network-check-target-ip-10-0-143-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-176.ec2.internal
      uid: 1b830d6f-a247-4c16-a3a1-b542ee500867
    resourceVersion: "54720"
    uid: 8d7dd95e-bb00-4f82-a92b-5221d431c48f
  spec:
    sourcePod: network-check-source-989f8b8dc-fm5jm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T15:24:31Z"
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.113074ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:52:31Z"
    - latency: 2.430859ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:51:31Z"
    - latency: 2.285825ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:50:31Z"
    - latency: 2.383155ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:49:31Z"
    - latency: 5.138241ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:48:31Z"
    - latency: 2.439181ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:47:31Z"
    - latency: 2.397922ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:46:31Z"
    - latency: 3.942567ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:45:31Z"
    - latency: 2.728612ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:44:31Z"
    - latency: 2.339196ms
      message: 'network-check-target-ip-10-0-143-112: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:43:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-03T15:17:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-176-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-176.ec2.internal
      uid: 1b830d6f-a247-4c16-a3a1-b542ee500867
    resourceVersion: "55585"
    uid: 34b8f4e1-3821-4735-93d8-764fa630572c
  spec:
    sourcePod: network-check-source-989f8b8dc-fm5jm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-03T15:23:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.264338ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:53:31Z"
    - latency: 2.057588ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:53:31Z"
    - latency: 769.261µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:52:31Z"
    - latency: 1.737766ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:52:31Z"
    - latency: 883.565µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:51:31Z"
    - latency: 1.98112ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:51:31Z"
    - latency: 883.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:50:31Z"
    - latency: 1.758622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:50:31Z"
    - latency: 813.178µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-03T15:49:31Z"
    - latency: 1.687333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-03T15:49:31Z"
kind: List
metadata:
  resourceVersion: ""