apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-231-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-231.ec2.internal
      uid: 2ba64925-cab9-4156-adb8-7237767751d1
    resourceVersion: "22031"
    uid: f09182d5-a4c1-4263-aac2-278bdc90f6df
  spec:
    sourcePod: network-check-source-989f8b8dc-btrll
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:57:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.017048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:11:51Z"
    - latency: 1.516136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:10:51Z"
    - latency: 1.145755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:09:51Z"
    - latency: 909.442µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:08:51Z"
    - latency: 846.08µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:51Z"
    - latency: 1.179531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:51Z"
    - latency: 1.589192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:51Z"
    - latency: 1.22568ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:51Z"
    - latency: 879.193µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:51Z"
    - latency: 825.883µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-231-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-231.ec2.internal
      uid: 2ba64925-cab9-4156-adb8-7237767751d1
    resourceVersion: "20414"
    uid: a59daa81-4884-4a35-b9e6-2fb0435f26e8
  spec:
    sourcePod: network-check-source-989f8b8dc-btrll
    targetEndpoint: ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:56:51Z"
      message: 'load-balancer-api-external: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.259526ms
      message: 'load-balancer-api-external: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:08:51Z"
    - latency: 10.590818ms
      message: 'load-balancer-api-external: resolved host name ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:08:51Z"
    - latency: 4.711367ms
      message: 'load-balancer-api-external: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:51Z"
    - latency: 6.831931ms
      message: 'load-balancer-api-external: resolved host name ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:07:51Z"
    - latency: 5.26722ms
      message: 'load-balancer-api-external: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:51Z"
    - latency: 8.261974ms
      message: 'load-balancer-api-external: resolved host name ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:51Z"
    - latency: 6.44356ms
      message: 'load-balancer-api-external: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:51Z"
    - latency: 7.877409ms
      message: 'load-balancer-api-external: resolved host name ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:51Z"
    - latency: 4.943656ms
      message: 'load-balancer-api-external: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:51Z"
    - latency: 7.359714ms
      message: 'load-balancer-api-external: resolved host name ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-231-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-231.ec2.internal
      uid: 2ba64925-cab9-4156-adb8-7237767751d1
    resourceVersion: "20415"
    uid: 10526844-6e37-449e-b08d-4157295e5cdd
  spec:
    sourcePod: network-check-source-989f8b8dc-btrll
    targetEndpoint: ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:56:51Z"
      message: 'load-balancer-api-internal: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.977157ms
      message: 'load-balancer-api-internal: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:08:51Z"
    - latency: 10.720809ms
      message: 'load-balancer-api-internal: resolved host name ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:08:51Z"
    - latency: 4.726791ms
      message: 'load-balancer-api-internal: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:51Z"
    - latency: 6.884167ms
      message: 'load-balancer-api-internal: resolved host name ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:07:51Z"
    - latency: 6.787143ms
      message: 'load-balancer-api-internal: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:51Z"
    - latency: 8.338242ms
      message: 'load-balancer-api-internal: resolved host name ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:51Z"
    - latency: 6.836665ms
      message: 'load-balancer-api-internal: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:51Z"
    - latency: 7.934532ms
      message: 'load-balancer-api-internal: resolved host name ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:51Z"
    - latency: 4.994351ms
      message: 'load-balancer-api-internal: tcp connection to ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:51Z"
    - latency: 7.326144ms
      message: 'load-balancer-api-internal: resolved host name ae4b10a1d26304c90bc6957201d5dcf9-fe7cb6b36c2773c0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-231-to-network-check-target-ip-10-0-131-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-231.ec2.internal
      uid: 2ba64925-cab9-4156-adb8-7237767751d1
    resourceVersion: "22030"
    uid: 34839f97-065a-460a-be38-88f988c40c26
  spec:
    sourcePod: network-check-source-989f8b8dc-btrll
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:57:51Z"
      message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.180506ms
      message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:11:51Z"
    - latency: 2.485759ms
      message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:10:51Z"
    - latency: 2.206981ms
      message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:09:51Z"
    - latency: 2.052759ms
      message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:08:51Z"
    - latency: 2.115209ms
      message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:51Z"
    - latency: 2.426013ms
      message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:51Z"
    - latency: 2.379081ms
      message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:51Z"
    - latency: 2.231217ms
      message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:51Z"
    - latency: 2.292041ms
      message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:51Z"
    - latency: 2.404278ms
      message: 'network-check-target-ip-10-0-131-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-231-to-network-check-target-ip-10-0-139-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-231.ec2.internal
      uid: 2ba64925-cab9-4156-adb8-7237767751d1
    resourceVersion: "22029"
    uid: 9947b5f7-13b7-4db2-b904-90570668b9ac
  spec:
    sourcePod: network-check-source-989f8b8dc-btrll
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:57:51Z"
      message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.183575ms
      message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:11:51Z"
    - latency: 997.451µs
      message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:10:51Z"
    - latency: 1.010974ms
      message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:09:51Z"
    - latency: 923.221µs
      message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:08:51Z"
    - latency: 1.286265ms
      message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:51Z"
    - latency: 1.091976ms
      message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:51Z"
    - latency: 1.046914ms
      message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:51Z"
    - latency: 1.262818ms
      message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:51Z"
    - latency: 959.46µs
      message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:51Z"
    - latency: 1.058059ms
      message: 'network-check-target-ip-10-0-139-231: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-231-to-network-check-target-ip-10-0-141-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-231.ec2.internal
      uid: 2ba64925-cab9-4156-adb8-7237767751d1
    resourceVersion: "22028"
    uid: f46450b6-1927-43c3-bdbc-d9bceafbdbf5
  spec:
    sourcePod: network-check-source-989f8b8dc-btrll
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:57:51Z"
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.843723ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:11:51Z"
    - latency: 2.031395ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:10:51Z"
    - latency: 1.874656ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:09:51Z"
    - latency: 1.663826ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:08:51Z"
    - latency: 1.76179ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:51Z"
    - latency: 2.000864ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:51Z"
    - latency: 2.102323ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:51Z"
    - latency: 2.103791ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:51Z"
    - latency: 1.897654ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:51Z"
    - latency: 1.937336ms
      message: 'network-check-target-ip-10-0-141-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-231-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-231.ec2.internal
      uid: 2ba64925-cab9-4156-adb8-7237767751d1
    resourceVersion: "20413"
    uid: e76bc148-55d5-49b6-886e-b2113f1a320e
  spec:
    sourcePod: network-check-source-989f8b8dc-btrll
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:56:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 774.51µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:08:51Z"
    - latency: 2.003369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:08:51Z"
    - latency: 1.004924ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:51Z"
    - latency: 1.77629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:07:51Z"
    - latency: 1.226132ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:51Z"
    - latency: 2.103362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:51Z"
    - latency: 1.161596ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:51Z"
    - latency: 2.355403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:51Z"
    - latency: 1.102369ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:51Z"
    - latency: 2.132023ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:51Z"
kind: List
metadata:
  resourceVersion: ""