apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:34:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: 79ab561f-0952-49f8-aa58-2ef000760902
    resourceVersion: "56378"
    uid: 763b0618-915e-4e26-bc2a-3ec1f8f016ea
  spec:
    sourcePod: network-check-source-989f8b8dc-mzh47
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:41:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.321456ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:09:15Z"
    - latency: 1.273515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:08:15Z"
    - latency: 718.756µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:07:15Z"
    - latency: 856.991µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:06:15Z"
    - latency: 953.76µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:15Z"
    - latency: 958.305µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:15Z"
    - latency: 1.093547ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:15Z"
    - latency: 1.609748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:15Z"
    - latency: 1.269454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:15Z"
    - latency: 1.104369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:34:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: 79ab561f-0952-49f8-aa58-2ef000760902
    resourceVersion: "57353"
    uid: aab217dd-8766-4694-bd10-446ebe70e529
  spec:
    sourcePod: network-check-source-989f8b8dc-mzh47
    targetEndpoint: ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:40:15Z"
      message: 'load-balancer-api-external: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.344104ms
      message: 'load-balancer-api-external: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:10:15Z"
    - latency: 6.811643ms
      message: 'load-balancer-api-external: resolved host name ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:10:15Z"
    - latency: 4.434423ms
      message: 'load-balancer-api-external: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:09:15Z"
    - latency: 7.583326ms
      message: 'load-balancer-api-external: resolved host name ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:09:15Z"
    - latency: 4.82553ms
      message: 'load-balancer-api-external: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:08:15Z"
    - latency: 7.00295ms
      message: 'load-balancer-api-external: resolved host name ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:08:15Z"
    - latency: 4.652246ms
      message: 'load-balancer-api-external: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:07:15Z"
    - latency: 6.983219ms
      message: 'load-balancer-api-external: resolved host name ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:07:15Z"
    - latency: 4.54482ms
      message: 'load-balancer-api-external: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:06:15Z"
    - latency: 7.228297ms
      message: 'load-balancer-api-external: resolved host name ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:06:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:34:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: 79ab561f-0952-49f8-aa58-2ef000760902
    resourceVersion: "57354"
    uid: ac5e11c9-3e11-4947-92c6-1ccb74861bbb
  spec:
    sourcePod: network-check-source-989f8b8dc-mzh47
    targetEndpoint: ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:40:15Z"
      message: 'load-balancer-api-internal: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.45684ms
      message: 'load-balancer-api-internal: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:10:15Z"
    - latency: 6.795215ms
      message: 'load-balancer-api-internal: resolved host name ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:10:15Z"
    - latency: 5.33712ms
      message: 'load-balancer-api-internal: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:09:15Z"
    - latency: 7.541505ms
      message: 'load-balancer-api-internal: resolved host name ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:09:15Z"
    - latency: 3.743135ms
      message: 'load-balancer-api-internal: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:08:15Z"
    - latency: 6.939904ms
      message: 'load-balancer-api-internal: resolved host name ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:08:15Z"
    - latency: 4.737348ms
      message: 'load-balancer-api-internal: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:07:15Z"
    - latency: 6.912121ms
      message: 'load-balancer-api-internal: resolved host name ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:07:15Z"
    - latency: 4.050131ms
      message: 'load-balancer-api-internal: tcp connection to ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:06:15Z"
    - latency: 7.246202ms
      message: 'load-balancer-api-internal: resolved host name ac720035ad13a4a90950125873a9d064-57a8170c85a98e9d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:06:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:34:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-network-check-target-ip-10-0-129-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: 79ab561f-0952-49f8-aa58-2ef000760902
    resourceVersion: "56375"
    uid: 2fcd20c2-ad41-46ca-8fe7-9c9eed4dd757
  spec:
    sourcePod: network-check-source-989f8b8dc-mzh47
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:41:15Z"
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.607µs
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:09:15Z"
    - latency: 1.05468ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:08:15Z"
    - latency: 1.166168ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:07:15Z"
    - latency: 1.089386ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:06:15Z"
    - latency: 935.332µs
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:15Z"
    - latency: 1.205274ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:15Z"
    - latency: 1.36834ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:15Z"
    - latency: 914.628µs
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:15Z"
    - latency: 870.801µs
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:15Z"
    - latency: 1.363709ms
      message: 'network-check-target-ip-10-0-129-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:34:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-network-check-target-ip-10-0-135-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: 79ab561f-0952-49f8-aa58-2ef000760902
    resourceVersion: "56377"
    uid: 80ed09d9-0254-4f32-b852-370c54f23d3c
  spec:
    sourcePod: network-check-source-989f8b8dc-mzh47
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:41:15Z"
      message: 'network-check-target-ip-10-0-135-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.331543ms
      message: 'network-check-target-ip-10-0-135-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:09:15Z"
    - latency: 2.352415ms
      message: 'network-check-target-ip-10-0-135-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:08:15Z"
    - latency: 2.348123ms
      message: 'network-check-target-ip-10-0-135-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:07:15Z"
    - latency: 2.298091ms
      message: 'network-check-target-ip-10-0-135-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:06:15Z"
    - latency: 2.633827ms
      message: 'network-check-target-ip-10-0-135-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:15Z"
    - latency: 2.494377ms
      message: 'network-check-target-ip-10-0-135-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:15Z"
    - latency: 2.503721ms
      message: 'network-check-target-ip-10-0-135-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:15Z"
    - latency: 2.360492ms
      message: 'network-check-target-ip-10-0-135-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:15Z"
    - latency: 2.355304ms
      message: 'network-check-target-ip-10-0-135-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:15Z"
    - latency: 2.307762ms
      message: 'network-check-target-ip-10-0-135-78: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:34:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-network-check-target-ip-10-0-139-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: 79ab561f-0952-49f8-aa58-2ef000760902
    resourceVersion: "56376"
    uid: 3985fab2-148c-4f25-8cbe-f4d1d6b351fa
  spec:
    sourcePod: network-check-source-989f8b8dc-mzh47
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:41:15Z"
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.091334ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:09:15Z"
    - latency: 2.080991ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:08:15Z"
    - latency: 2.001446ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:07:15Z"
    - latency: 2.210462ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:06:15Z"
    - latency: 2.643534ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:15Z"
    - latency: 2.170295ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:15Z"
    - latency: 2.338274ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:15Z"
    - latency: 2.514398ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:15Z"
    - latency: 2.141084ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:15Z"
    - latency: 1.95497ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:34:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-12-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-12.ec2.internal
      uid: 79ab561f-0952-49f8-aa58-2ef000760902
    resourceVersion: "57352"
    uid: bfce04a8-7cbf-443f-89a5-fa54530cc00d
  spec:
    sourcePod: network-check-source-989f8b8dc-mzh47
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:40:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.027892ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:10:15Z"
    - latency: 2.131266ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:10:15Z"
    - latency: 1.010209ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:09:15Z"
    - latency: 2.338855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:09:15Z"
    - latency: 866.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:08:15Z"
    - latency: 1.868873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:08:15Z"
    - latency: 802.98µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:07:15Z"
    - latency: 2.036934ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:07:15Z"
    - latency: 882.394µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:06:15Z"
    - latency: 1.785009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:06:15Z"
kind: List
metadata:
  resourceVersion: ""