apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T20:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-70-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-70.ec2.internal
      uid: 1f304389-64c8-44b7-bd43-c7413873427f
    resourceVersion: "53328"
    uid: 2c2fad37-3f9a-4b4b-b990-932e21e2fd5b
  spec:
    sourcePod: network-check-source-989f8b8dc-jb2tw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T20:11:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.081328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:39:40Z"
    - latency: 1.026743ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:38:40Z"
    - latency: 1.318758ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:37:40Z"
    - latency: 1.15961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:36:40Z"
    - latency: 1.672708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:35:40Z"
    - latency: 948.451µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:34:40Z"
    - latency: 1.19386ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:33:40Z"
    - latency: 1.272394ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:32:40Z"
    - latency: 1.109477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:31:40Z"
    - latency: 1.383034ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:30:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T20:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-70-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-70.ec2.internal
      uid: 1f304389-64c8-44b7-bd43-c7413873427f
    resourceVersion: "48518"
    uid: 62c6021d-e22d-4fce-a16b-86d75b031a1c
  spec:
    sourcePod: network-check-source-989f8b8dc-jb2tw
    targetEndpoint: a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T20:10:40Z"
      message: 'load-balancer-api-external: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.624255ms
      message: 'load-balancer-api-external: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:34:40Z"
    - latency: 9.049389ms
      message: 'load-balancer-api-external: resolved host name a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:34:40Z"
    - latency: 5.069407ms
      message: 'load-balancer-api-external: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:33:40Z"
    - latency: 8.058223ms
      message: 'load-balancer-api-external: resolved host name a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:33:40Z"
    - latency: 4.000082ms
      message: 'load-balancer-api-external: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:32:40Z"
    - latency: 7.867002ms
      message: 'load-balancer-api-external: resolved host name a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:32:40Z"
    - latency: 4.211529ms
      message: 'load-balancer-api-external: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:31:40Z"
    - latency: 6.728473ms
      message: 'load-balancer-api-external: resolved host name a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:31:40Z"
    - latency: 3.747102ms
      message: 'load-balancer-api-external: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:30:40Z"
    - latency: 7.718575ms
      message: 'load-balancer-api-external: resolved host name a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:30:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T20:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-70-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-70.ec2.internal
      uid: 1f304389-64c8-44b7-bd43-c7413873427f
    resourceVersion: "48519"
    uid: 92a9d112-3a69-47a8-a4dd-bccbed36e2d1
  spec:
    sourcePod: network-check-source-989f8b8dc-jb2tw
    targetEndpoint: a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T20:10:40Z"
      message: 'load-balancer-api-internal: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.612906ms
      message: 'load-balancer-api-internal: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:34:40Z"
    - latency: 9.159467ms
      message: 'load-balancer-api-internal: resolved host name a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:34:40Z"
    - latency: 3.745354ms
      message: 'load-balancer-api-internal: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:33:40Z"
    - latency: 8.01856ms
      message: 'load-balancer-api-internal: resolved host name a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:33:40Z"
    - latency: 3.599933ms
      message: 'load-balancer-api-internal: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:32:40Z"
    - latency: 7.979737ms
      message: 'load-balancer-api-internal: resolved host name a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:32:40Z"
    - latency: 4.229883ms
      message: 'load-balancer-api-internal: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:31:40Z"
    - latency: 6.537944ms
      message: 'load-balancer-api-internal: resolved host name a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:31:40Z"
    - latency: 3.727115ms
      message: 'load-balancer-api-internal: tcp connection to a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:30:40Z"
    - latency: 7.832985ms
      message: 'load-balancer-api-internal: resolved host name a5e9f415837c3486d9a250b0b7dca81c-6bbae182b89fd3e9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:30:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T20:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-70-to-network-check-target-ip-10-0-132-18
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-70.ec2.internal
      uid: 1f304389-64c8-44b7-bd43-c7413873427f
    resourceVersion: "53327"
    uid: 24bc6525-9e44-47cc-9e0c-eda03fe2190d
  spec:
    sourcePod: network-check-source-989f8b8dc-jb2tw
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T20:11:40Z"
      message: 'network-check-target-ip-10-0-132-18: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.868162ms
      message: 'network-check-target-ip-10-0-132-18: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:39:40Z"
    - latency: 1.973131ms
      message: 'network-check-target-ip-10-0-132-18: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:38:40Z"
    - latency: 1.88999ms
      message: 'network-check-target-ip-10-0-132-18: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:37:40Z"
    - latency: 1.549031ms
      message: 'network-check-target-ip-10-0-132-18: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:36:40Z"
    - latency: 2.035126ms
      message: 'network-check-target-ip-10-0-132-18: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:35:40Z"
    - latency: 1.916709ms
      message: 'network-check-target-ip-10-0-132-18: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:34:40Z"
    - latency: 1.595274ms
      message: 'network-check-target-ip-10-0-132-18: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:33:40Z"
    - latency: 1.800746ms
      message: 'network-check-target-ip-10-0-132-18: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:32:40Z"
    - latency: 1.793251ms
      message: 'network-check-target-ip-10-0-132-18: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:31:40Z"
    - latency: 1.830063ms
      message: 'network-check-target-ip-10-0-132-18: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:30:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T20:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-70-to-network-check-target-ip-10-0-136-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-70.ec2.internal
      uid: 1f304389-64c8-44b7-bd43-c7413873427f
    resourceVersion: "53325"
    uid: 505b959e-a6c2-4ee6-aeae-4db86895fe52
  spec:
    sourcePod: network-check-source-989f8b8dc-jb2tw
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T20:11:40Z"
      message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.432µs
      message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:39:40Z"
    - latency: 1.244702ms
      message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:38:40Z"
    - latency: 1.244436ms
      message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:37:40Z"
    - latency: 1.024177ms
      message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:36:40Z"
    - latency: 1.627015ms
      message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:35:40Z"
    - latency: 1.358446ms
      message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:34:40Z"
    - latency: 1.492582ms
      message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:33:40Z"
    - latency: 980.127µs
      message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:32:40Z"
    - latency: 1.377304ms
      message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:31:40Z"
    - latency: 1.119364ms
      message: 'network-check-target-ip-10-0-136-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:30:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T20:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-70-to-network-check-target-ip-10-0-138-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-70.ec2.internal
      uid: 1f304389-64c8-44b7-bd43-c7413873427f
    resourceVersion: "53326"
    uid: 66c9eec4-8d4b-4cf9-ab7a-79e372644f0d
  spec:
    sourcePod: network-check-source-989f8b8dc-jb2tw
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T20:11:40Z"
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.04389ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:39:40Z"
    - latency: 1.949703ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:38:40Z"
    - latency: 1.85561ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:37:40Z"
    - latency: 2.038867ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:36:40Z"
    - latency: 2.109291ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:35:40Z"
    - latency: 2.312612ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:34:40Z"
    - latency: 1.977654ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:33:40Z"
    - latency: 2.334671ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:32:40Z"
    - latency: 2.034099ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:31:40Z"
    - latency: 1.97454ms
      message: 'network-check-target-ip-10-0-138-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:30:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T20:04:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-70-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-70.ec2.internal
      uid: 1f304389-64c8-44b7-bd43-c7413873427f
    resourceVersion: "48517"
    uid: b8b389a5-0977-49cd-9cb0-8b0d944c79aa
  spec:
    sourcePod: network-check-source-989f8b8dc-jb2tw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T20:10:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.259285ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:34:40Z"
    - latency: 1.888888ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:34:40Z"
    - latency: 889.871µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:33:40Z"
    - latency: 1.945495ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:33:40Z"
    - latency: 938.262µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:32:40Z"
    - latency: 1.820011ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:32:40Z"
    - latency: 810.185µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:31:40Z"
    - latency: 1.980105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:31:40Z"
    - latency: 982.498µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T20:30:40Z"
    - latency: 2.505488ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T20:30:40Z"
kind: List
metadata:
  resourceVersion: ""