apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T17:30:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 52208722-8707-476b-945f-df338a6e2a1a
    resourceVersion: "61574"
    uid: ce46cc93-eb61-4a5c-8349-0098da525b51
  spec:
    sourcePod: network-check-source-869dcfcdcd-ckl8p
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T17:37:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.159531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:12:10Z"
    - latency: 992.767µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:11:10Z"
    - latency: 1.196103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:10:10Z"
    - latency: 878.493µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:09:10Z"
    - latency: 1.23971ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:08:10Z"
    - latency: 1.130332ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:07:10Z"
    - latency: 1.025527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:06:10Z"
    - latency: 1.044923ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:05:10Z"
    - latency: 1.129885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:04:10Z"
    - latency: 1.343451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:03:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T17:30:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 52208722-8707-476b-945f-df338a6e2a1a
    resourceVersion: "61578"
    uid: 010922f1-853e-45e7-b61c-574015262a5a
  spec:
    sourcePod: network-check-source-869dcfcdcd-ckl8p
    targetEndpoint: a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T17:36:10Z"
      message: 'load-balancer-api-external: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.988848ms
      message: 'load-balancer-api-external: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:12:10Z"
    - latency: 7.428672ms
      message: 'load-balancer-api-external: resolved host name a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:12:10Z"
    - latency: 4.541301ms
      message: 'load-balancer-api-external: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:11:10Z"
    - latency: 7.248158ms
      message: 'load-balancer-api-external: resolved host name a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:11:10Z"
    - latency: 5.457062ms
      message: 'load-balancer-api-external: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:10:10Z"
    - latency: 7.67901ms
      message: 'load-balancer-api-external: resolved host name a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:10:10Z"
    - latency: 4.334509ms
      message: 'load-balancer-api-external: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:09:10Z"
    - latency: 6.441093ms
      message: 'load-balancer-api-external: resolved host name a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:09:10Z"
    - latency: 8.703858ms
      message: 'load-balancer-api-external: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:08:10Z"
    - latency: 8.987297ms
      message: 'load-balancer-api-external: resolved host name a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:08:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T17:30:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 52208722-8707-476b-945f-df338a6e2a1a
    resourceVersion: "61579"
    uid: d0320eb0-921e-40a4-9285-40e15de23fdb
  spec:
    sourcePod: network-check-source-869dcfcdcd-ckl8p
    targetEndpoint: a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T17:36:10Z"
      message: 'load-balancer-api-internal: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 12.469536ms
      message: 'load-balancer-api-internal: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:12:10Z"
    - latency: 7.38015ms
      message: 'load-balancer-api-internal: resolved host name a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:12:10Z"
    - latency: 4.554353ms
      message: 'load-balancer-api-internal: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:11:10Z"
    - latency: 7.187648ms
      message: 'load-balancer-api-internal: resolved host name a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:11:10Z"
    - latency: 5.173545ms
      message: 'load-balancer-api-internal: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:10:10Z"
    - latency: 7.696945ms
      message: 'load-balancer-api-internal: resolved host name a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:10:10Z"
    - latency: 3.555261ms
      message: 'load-balancer-api-internal: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:09:10Z"
    - latency: 6.351302ms
      message: 'load-balancer-api-internal: resolved host name a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:09:10Z"
    - latency: 5.303185ms
      message: 'load-balancer-api-internal: tcp connection to a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:08:10Z"
    - latency: 9.019146ms
      message: 'load-balancer-api-internal: resolved host name a06acc1f866aa40e884548b34092575c-9f193b9156c97d26.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:08:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T17:30:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-network-check-target-ip-10-0-132-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 52208722-8707-476b-945f-df338a6e2a1a
    resourceVersion: "61575"
    uid: b9ba95a1-c5bf-4a1d-a006-0225cf34b3b5
  spec:
    sourcePod: network-check-source-869dcfcdcd-ckl8p
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T17:37:10Z"
      message: 'network-check-target-ip-10-0-132-13: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.256112ms
      message: 'network-check-target-ip-10-0-132-13: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:12:10Z"
    - latency: 2.261833ms
      message: 'network-check-target-ip-10-0-132-13: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:11:10Z"
    - latency: 2.242332ms
      message: 'network-check-target-ip-10-0-132-13: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:10:10Z"
    - latency: 2.567381ms
      message: 'network-check-target-ip-10-0-132-13: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:09:10Z"
    - latency: 2.382058ms
      message: 'network-check-target-ip-10-0-132-13: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:08:10Z"
    - latency: 2.46566ms
      message: 'network-check-target-ip-10-0-132-13: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:07:10Z"
    - latency: 2.541402ms
      message: 'network-check-target-ip-10-0-132-13: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:06:10Z"
    - latency: 2.242585ms
      message: 'network-check-target-ip-10-0-132-13: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:05:10Z"
    - latency: 2.779093ms
      message: 'network-check-target-ip-10-0-132-13: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:04:10Z"
    - latency: 2.108533ms
      message: 'network-check-target-ip-10-0-132-13: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:03:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T17:30:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-network-check-target-ip-10-0-138-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 52208722-8707-476b-945f-df338a6e2a1a
    resourceVersion: "61576"
    uid: 1f5feadb-8f18-4b26-959e-1370a6b2af7e
  spec:
    sourcePod: network-check-source-869dcfcdcd-ckl8p
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T17:37:10Z"
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.204156ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:12:10Z"
    - latency: 2.769613ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:11:10Z"
    - latency: 2.401183ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:10:10Z"
    - latency: 2.005472ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:09:10Z"
    - latency: 2.413754ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:08:10Z"
    - latency: 2.308981ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:07:10Z"
    - latency: 2.178473ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:06:10Z"
    - latency: 2.250418ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:05:10Z"
    - latency: 2.369086ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:04:10Z"
    - latency: 1.964493ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:03:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T17:30:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-network-check-target-ip-10-0-139-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 52208722-8707-476b-945f-df338a6e2a1a
    resourceVersion: "61573"
    uid: 1f55ad51-1c69-4f4d-957d-78abd25cb684
  spec:
    sourcePod: network-check-source-869dcfcdcd-ckl8p
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T17:37:10Z"
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.013168ms
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:12:10Z"
    - latency: 1.297707ms
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:11:10Z"
    - latency: 911.673µs
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:10:10Z"
    - latency: 889.453µs
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:09:10Z"
    - latency: 1.229466ms
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:08:10Z"
    - latency: 1.14811ms
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:07:10Z"
    - latency: 1.004078ms
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:06:10Z"
    - latency: 998.594µs
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:05:10Z"
    - latency: 1.577903ms
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:04:10Z"
    - latency: 855.869µs
      message: 'network-check-target-ip-10-0-139-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:03:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T17:30:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-16-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-16.ec2.internal
      uid: 52208722-8707-476b-945f-df338a6e2a1a
    resourceVersion: "61577"
    uid: 06a2068a-1eda-4490-9e4e-3774bf8d068b
  spec:
    sourcePod: network-check-source-869dcfcdcd-ckl8p
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T17:36:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.409µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:12:10Z"
    - latency: 1.688349ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:12:10Z"
    - latency: 1.260618ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:11:10Z"
    - latency: 1.729076ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:11:10Z"
    - latency: 917.978µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:10:10Z"
    - latency: 1.71635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:10:10Z"
    - latency: 1.190299ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:09:10Z"
    - latency: 1.7095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:09:10Z"
    - latency: 858.9µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T18:08:10Z"
    - latency: 2.031999ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T18:08:10Z"
kind: List
metadata:
  resourceVersion: ""