apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-118-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-118.ec2.internal
      uid: e1e8322d-3ca5-40f5-951c-25d81f001e93
    resourceVersion: "32148"
    uid: e3c29a2a-bfc2-40f0-ab96-677bea205b1c
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzsbm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T20:59:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 902.081µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:34:30Z"
    - latency: 1.152675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:33:30Z"
    - latency: 1.018789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:32:30Z"
    - latency: 894.44µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:31:30Z"
    - latency: 1.078548ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:30:30Z"
    - latency: 1.182971ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:29:30Z"
    - latency: 1.054294ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:28:30Z"
    - latency: 1.093616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:27:30Z"
    - latency: 1.126911ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:26:30Z"
    - latency: 1.289598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:25:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-118-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-118.ec2.internal
      uid: e1e8322d-3ca5-40f5-951c-25d81f001e93
    resourceVersion: "32150"
    uid: 4a173bb8-0ac0-4ead-bb5d-e50eedf4cab8
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzsbm
    targetEndpoint: a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T20:58:30Z"
      message: 'load-balancer-api-external: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.460393ms
      message: 'load-balancer-api-external: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:34:30Z"
    - latency: 8.565791ms
      message: 'load-balancer-api-external: resolved host name a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:34:30Z"
    - latency: 4.72788ms
      message: 'load-balancer-api-external: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:33:30Z"
    - latency: 9.489126ms
      message: 'load-balancer-api-external: resolved host name a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:33:30Z"
    - latency: 4.931585ms
      message: 'load-balancer-api-external: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:32:30Z"
    - latency: 7.619299ms
      message: 'load-balancer-api-external: resolved host name a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:32:30Z"
    - latency: 4.983558ms
      message: 'load-balancer-api-external: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:31:30Z"
    - latency: 8.495279ms
      message: 'load-balancer-api-external: resolved host name a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:31:30Z"
    - latency: 5.803074ms
      message: 'load-balancer-api-external: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:30:30Z"
    - latency: 7.860736ms
      message: 'load-balancer-api-external: resolved host name a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:30:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-118-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-118.ec2.internal
      uid: e1e8322d-3ca5-40f5-951c-25d81f001e93
    resourceVersion: "32149"
    uid: f50d2f22-693b-43e7-9461-570f9fd48ece
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzsbm
    targetEndpoint: a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T20:58:30Z"
      message: 'load-balancer-api-internal: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.413649ms
      message: 'load-balancer-api-internal: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:34:30Z"
    - latency: 8.534135ms
      message: 'load-balancer-api-internal: resolved host name a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:34:30Z"
    - latency: 4.746286ms
      message: 'load-balancer-api-internal: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:33:30Z"
    - latency: 9.452346ms
      message: 'load-balancer-api-internal: resolved host name a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:33:30Z"
    - latency: 5.495762ms
      message: 'load-balancer-api-internal: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:32:30Z"
    - latency: 7.584681ms
      message: 'load-balancer-api-internal: resolved host name a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:32:30Z"
    - latency: 5.562106ms
      message: 'load-balancer-api-internal: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:31:30Z"
    - latency: 8.464843ms
      message: 'load-balancer-api-internal: resolved host name a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:31:30Z"
    - latency: 5.066123ms
      message: 'load-balancer-api-internal: tcp connection to a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:30:30Z"
    - latency: 7.81804ms
      message: 'load-balancer-api-internal: resolved host name a8efbe220011c4c1ebe4b6c87c443983-b7ee78795d2443f4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:30:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-118-to-network-check-target-ip-10-0-138-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-118.ec2.internal
      uid: e1e8322d-3ca5-40f5-951c-25d81f001e93
    resourceVersion: "32147"
    uid: 45897ef3-8d89-4d94-80b6-bc0d0a25c26c
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzsbm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T20:59:30Z"
      message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.126548ms
      message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:34:30Z"
    - latency: 2.104726ms
      message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:33:30Z"
    - latency: 2.610168ms
      message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:32:30Z"
    - latency: 2.220162ms
      message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:31:30Z"
    - latency: 2.283667ms
      message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:30:30Z"
    - latency: 2.103461ms
      message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:29:30Z"
    - latency: 2.291944ms
      message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:28:30Z"
    - latency: 2.320088ms
      message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:27:30Z"
    - latency: 2.316063ms
      message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:26:30Z"
    - latency: 2.42298ms
      message: 'network-check-target-ip-10-0-138-134: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:25:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-118-to-network-check-target-ip-10-0-139-55
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-118.ec2.internal
      uid: e1e8322d-3ca5-40f5-951c-25d81f001e93
    resourceVersion: "32144"
    uid: 0861ec64-d144-454c-a8ce-2b192c3a5e94
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzsbm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T20:59:30Z"
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.99489ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:34:30Z"
    - latency: 2.17319ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:33:30Z"
    - latency: 2.639703ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:32:30Z"
    - latency: 2.333912ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:31:30Z"
    - latency: 3.126696ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:30:30Z"
    - latency: 2.345104ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:29:30Z"
    - latency: 2.488485ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:28:30Z"
    - latency: 2.297331ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:27:30Z"
    - latency: 2.782022ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:26:30Z"
    - latency: 2.167896ms
      message: 'network-check-target-ip-10-0-139-55: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:25:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-118-to-network-check-target-ip-10-0-140-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-118.ec2.internal
      uid: e1e8322d-3ca5-40f5-951c-25d81f001e93
    resourceVersion: "32145"
    uid: 920c6849-307a-4ae6-bb96-38a5aa3e79f7
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzsbm
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T20:59:30Z"
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.515034ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:34:30Z"
    - latency: 881.162µs
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:33:30Z"
    - latency: 1.339966ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:32:30Z"
    - latency: 915.901µs
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:31:30Z"
    - latency: 936.29µs
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:30:30Z"
    - latency: 945.39µs
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:29:30Z"
    - latency: 1.350737ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:28:30Z"
    - latency: 693.617µs
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:27:30Z"
    - latency: 907.519µs
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:26:30Z"
    - latency: 1.514432ms
      message: 'network-check-target-ip-10-0-140-118: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:25:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T20:52:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-118-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-118.ec2.internal
      uid: e1e8322d-3ca5-40f5-951c-25d81f001e93
    resourceVersion: "32146"
    uid: 081c4a0e-ab46-45d9-8919-a93bec99d549
  spec:
    sourcePod: network-check-source-7cbc45fddc-mzsbm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T20:58:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.02379ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:34:30Z"
    - latency: 1.920432ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:34:30Z"
    - latency: 1.368543ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:33:30Z"
    - latency: 1.738438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:33:30Z"
    - latency: 711.647µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:32:30Z"
    - latency: 1.658042ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:32:30Z"
    - latency: 823.518µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:31:30Z"
    - latency: 1.615738ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:31:30Z"
    - latency: 1.264019ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T21:30:30Z"
    - latency: 2.053403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T21:30:30Z"
kind: List
metadata:
  resourceVersion: ""