apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:55:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-32-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-32.ec2.internal
      uid: beaed731-94ae-4166-8e74-8e12a3e16522
    resourceVersion: "64033"
    uid: 73d375d6-616a-49cc-8eae-cfda97c224a4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7fwz4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T22:02:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.085832ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:37:58Z"
    - latency: 779.343µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:36:58Z"
    - latency: 1.363564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:35:58Z"
    - latency: 1.054536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:34:58Z"
    - latency: 867.434µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:33:58Z"
    - latency: 1.108711ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:32:58Z"
    - latency: 1.257578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:31:58Z"
    - latency: 1.293021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:30:58Z"
    - latency: 1.056949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:29:58Z"
    - latency: 1.501515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:28:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:55:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-32-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-32.ec2.internal
      uid: beaed731-94ae-4166-8e74-8e12a3e16522
    resourceVersion: "64035"
    uid: 136823ed-b673-4f95-98cb-390da7226499
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7fwz4
    targetEndpoint: a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T22:01:58Z"
      message: 'load-balancer-api-external: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.7981ms
      message: 'load-balancer-api-external: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:37:58Z"
    - latency: 7.27033ms
      message: 'load-balancer-api-external: resolved host name a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:37:58Z"
    - latency: 3.62145ms
      message: 'load-balancer-api-external: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:36:58Z"
    - latency: 9.508879ms
      message: 'load-balancer-api-external: resolved host name a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:36:58Z"
    - latency: 3.536515ms
      message: 'load-balancer-api-external: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:35:58Z"
    - latency: 9.004786ms
      message: 'load-balancer-api-external: resolved host name a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:35:58Z"
    - latency: 5.968708ms
      message: 'load-balancer-api-external: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:34:58Z"
    - latency: 9.796976ms
      message: 'load-balancer-api-external: resolved host name a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:34:58Z"
    - latency: 5.304298ms
      message: 'load-balancer-api-external: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:33:58Z"
    - latency: 11.930837ms
      message: 'load-balancer-api-external: resolved host name a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:33:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:55:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-32-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-32.ec2.internal
      uid: beaed731-94ae-4166-8e74-8e12a3e16522
    resourceVersion: "64034"
    uid: 4325af0a-e801-4436-85cc-b62c0d3d5935
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7fwz4
    targetEndpoint: a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T22:01:58Z"
      message: 'load-balancer-api-internal: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.12906ms
      message: 'load-balancer-api-internal: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:37:58Z"
    - latency: 7.217287ms
      message: 'load-balancer-api-internal: resolved host name a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:37:58Z"
    - latency: 3.605598ms
      message: 'load-balancer-api-internal: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:36:58Z"
    - latency: 9.559362ms
      message: 'load-balancer-api-internal: resolved host name a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:36:58Z"
    - latency: 3.581095ms
      message: 'load-balancer-api-internal: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:35:58Z"
    - latency: 8.971897ms
      message: 'load-balancer-api-internal: resolved host name a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:35:58Z"
    - latency: 5.95411ms
      message: 'load-balancer-api-internal: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:34:58Z"
    - latency: 9.752535ms
      message: 'load-balancer-api-internal: resolved host name a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:34:58Z"
    - latency: 5.378163ms
      message: 'load-balancer-api-internal: tcp connection to a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:33:58Z"
    - latency: 11.88198ms
      message: 'load-balancer-api-internal: resolved host name a6fc59ac0f54c4a16bd52ae915e00db8-e02f2bae27bb1424.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:33:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:55:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-32-to-network-check-target-ip-10-0-135-91
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-32.ec2.internal
      uid: beaed731-94ae-4166-8e74-8e12a3e16522
    resourceVersion: "64031"
    uid: 45714b5d-5859-4a6d-b1dc-6f620b01aab1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7fwz4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T22:02:58Z"
      message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.420642ms
      message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:37:58Z"
    - latency: 2.073326ms
      message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:36:58Z"
    - latency: 1.98566ms
      message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:35:58Z"
    - latency: 1.954686ms
      message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:34:58Z"
    - latency: 2.5812ms
      message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:33:58Z"
    - latency: 1.84508ms
      message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:32:58Z"
    - latency: 2.203094ms
      message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:31:58Z"
    - latency: 2.231504ms
      message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:30:58Z"
    - latency: 1.970476ms
      message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:29:58Z"
    - latency: 2.012003ms
      message: 'network-check-target-ip-10-0-135-91: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:28:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:55:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-32-to-network-check-target-ip-10-0-136-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-32.ec2.internal
      uid: beaed731-94ae-4166-8e74-8e12a3e16522
    resourceVersion: "64029"
    uid: 1cf02ef1-52aa-4f6c-954d-8274655428d4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7fwz4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T22:02:58Z"
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.410718ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:37:58Z"
    - latency: 1.784781ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:36:58Z"
    - latency: 2.15538ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:35:58Z"
    - latency: 1.996944ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:34:58Z"
    - latency: 3.017286ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:33:58Z"
    - latency: 1.970344ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:32:58Z"
    - latency: 2.558103ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:31:58Z"
    - latency: 2.464575ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:30:58Z"
    - latency: 2.344097ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:29:58Z"
    - latency: 2.241711ms
      message: 'network-check-target-ip-10-0-136-157: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:28:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:55:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-32-to-network-check-target-ip-10-0-139-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-32.ec2.internal
      uid: beaed731-94ae-4166-8e74-8e12a3e16522
    resourceVersion: "64030"
    uid: 70647a21-8f02-433f-9c92-0127f75060b8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7fwz4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T22:02:58Z"
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.495499ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:37:58Z"
    - latency: 1.024284ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:36:58Z"
    - latency: 1.335469ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:35:58Z"
    - latency: 957.059µs
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:34:58Z"
    - latency: 1.287594ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:33:58Z"
    - latency: 865.079µs
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:32:58Z"
    - latency: 921.602µs
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:31:58Z"
    - latency: 1.362713ms
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:30:58Z"
    - latency: 946.98µs
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:29:58Z"
    - latency: 899.006µs
      message: 'network-check-target-ip-10-0-139-32: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:28:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T21:55:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-32-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-32.ec2.internal
      uid: beaed731-94ae-4166-8e74-8e12a3e16522
    resourceVersion: "64032"
    uid: 03f6c86c-9a67-4f62-a4f3-b37e3d8feb2f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-7fwz4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T22:01:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 945.285µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:37:58Z"
    - latency: 2.423428ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:37:58Z"
    - latency: 949.235µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:36:58Z"
    - latency: 1.963404ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:36:58Z"
    - latency: 1.261475ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:35:58Z"
    - latency: 1.739876ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:35:58Z"
    - latency: 1.030263ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:34:58Z"
    - latency: 2.461561ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:34:58Z"
    - latency: 859.015µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T22:33:58Z"
    - latency: 1.985241ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T22:33:58Z"
kind: List
metadata:
  resourceVersion: ""