apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:41:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 1dff9ebf-56cb-47dc-8415-424d7e4bd1cb
    resourceVersion: "62586"
    uid: a5af5ce5-1127-440f-bc33-2ef5f6881c1d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdzvp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:48:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.080246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:23:48Z"
    - latency: 1.219129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:22:48Z"
    - latency: 1.016702ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:21:48Z"
    - latency: 860.134µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:20:48Z"
    - latency: 1.125911ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:19:48Z"
    - latency: 4.941204ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:18:48Z"
    - latency: 931.966µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:17:48Z"
    - latency: 1.054122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:16:48Z"
    - latency: 1.279333ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:15:48Z"
    - latency: 1.188222ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:14:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:41:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 1dff9ebf-56cb-47dc-8415-424d7e4bd1cb
    resourceVersion: "62588"
    uid: 503889d6-0413-4a2d-9cc2-094f9876ab1f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdzvp
    targetEndpoint: aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:47:48Z"
      message: 'load-balancer-api-external: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.113901ms
      message: 'load-balancer-api-external: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:23:48Z"
    - latency: 8.181769ms
      message: 'load-balancer-api-external: resolved host name aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:23:48Z"
    - latency: 4.689138ms
      message: 'load-balancer-api-external: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:22:48Z"
    - latency: 8.56932ms
      message: 'load-balancer-api-external: resolved host name aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:22:48Z"
    - latency: 5.063316ms
      message: 'load-balancer-api-external: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:21:48Z"
    - latency: 7.886038ms
      message: 'load-balancer-api-external: resolved host name aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:21:48Z"
    - latency: 4.429159ms
      message: 'load-balancer-api-external: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:20:48Z"
    - latency: 8.380121ms
      message: 'load-balancer-api-external: resolved host name aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:20:48Z"
    - latency: 3.738022ms
      message: 'load-balancer-api-external: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:19:48Z"
    - latency: 8.906216ms
      message: 'load-balancer-api-external: resolved host name aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:19:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:41:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 1dff9ebf-56cb-47dc-8415-424d7e4bd1cb
    resourceVersion: "62589"
    uid: 0dd36712-45ed-48e7-bc55-923a034b1349
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdzvp
    targetEndpoint: aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:47:48Z"
      message: 'load-balancer-api-internal: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.014811ms
      message: 'load-balancer-api-internal: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:23:48Z"
    - latency: 8.11272ms
      message: 'load-balancer-api-internal: resolved host name aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:23:48Z"
    - latency: 4.687106ms
      message: 'load-balancer-api-internal: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:22:48Z"
    - latency: 8.540065ms
      message: 'load-balancer-api-internal: resolved host name aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:22:48Z"
    - latency: 5.071701ms
      message: 'load-balancer-api-internal: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:21:48Z"
    - latency: 7.811348ms
      message: 'load-balancer-api-internal: resolved host name aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:21:48Z"
    - latency: 4.653401ms
      message: 'load-balancer-api-internal: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:20:48Z"
    - latency: 8.473869ms
      message: 'load-balancer-api-internal: resolved host name aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:20:48Z"
    - latency: 3.714656ms
      message: 'load-balancer-api-internal: tcp connection to aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:19:48Z"
    - latency: 8.983102ms
      message: 'load-balancer-api-internal: resolved host name aaba8f04dcd7342f3bffa324e889eeda-795a2e484ceae8f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:19:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:41:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-network-check-target-ip-10-0-128-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 1dff9ebf-56cb-47dc-8415-424d7e4bd1cb
    resourceVersion: "62584"
    uid: e797b734-7080-4962-9edb-642e09853e0a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdzvp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:48:48Z"
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.959781ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:23:48Z"
    - latency: 1.648265ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:22:48Z"
    - latency: 2.052918ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:21:48Z"
    - latency: 1.693967ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:20:48Z"
    - latency: 1.973883ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:19:48Z"
    - latency: 4.287729ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:18:48Z"
    - latency: 2.358106ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:17:48Z"
    - latency: 2.108903ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:16:48Z"
    - latency: 2.187607ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:15:48Z"
    - latency: 1.955948ms
      message: 'network-check-target-ip-10-0-128-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:14:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:41:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-network-check-target-ip-10-0-131-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 1dff9ebf-56cb-47dc-8415-424d7e4bd1cb
    resourceVersion: "62582"
    uid: 9e47aca8-c2ea-467b-9ed9-01411747cc85
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdzvp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:48:48Z"
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.033024ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:23:48Z"
    - latency: 904.736µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:22:48Z"
    - latency: 883.568µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:21:48Z"
    - latency: 914.25µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:20:48Z"
    - latency: 979.492µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:19:48Z"
    - latency: 4.298559ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:18:48Z"
    - latency: 1.100414ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:17:48Z"
    - latency: 944.713µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:16:48Z"
    - latency: 795.825µs
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:15:48Z"
    - latency: 1.185559ms
      message: 'network-check-target-ip-10-0-131-139: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:14:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:41:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-network-check-target-ip-10-0-134-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 1dff9ebf-56cb-47dc-8415-424d7e4bd1cb
    resourceVersion: "62583"
    uid: 8b42a04d-d41b-4711-97f1-288f1f37f237
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdzvp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:48:48Z"
      message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.977837ms
      message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:23:48Z"
    - latency: 2.181785ms
      message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:22:48Z"
    - latency: 2.162713ms
      message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:21:48Z"
    - latency: 2.012211ms
      message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:20:48Z"
    - latency: 2.290824ms
      message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:19:48Z"
    - latency: 4.759566ms
      message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:18:48Z"
    - latency: 2.308863ms
      message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:17:48Z"
    - latency: 2.213955ms
      message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:16:48Z"
    - latency: 2.203654ms
      message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:15:48Z"
    - latency: 2.072913ms
      message: 'network-check-target-ip-10-0-134-120: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:14:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T13:41:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-139.ec2.internal
      uid: 1dff9ebf-56cb-47dc-8415-424d7e4bd1cb
    resourceVersion: "62585"
    uid: c89fa52c-9626-4330-9d64-0e2463efb4d5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-pdzvp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T13:47:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 769.49µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:23:48Z"
    - latency: 2.046096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:23:48Z"
    - latency: 1.456624ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:22:48Z"
    - latency: 1.764062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:22:48Z"
    - latency: 917.494µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:21:48Z"
    - latency: 1.607528ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:21:48Z"
    - latency: 811.153µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:20:48Z"
    - latency: 1.703071ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:20:48Z"
    - latency: 1.072017ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T14:19:48Z"
    - latency: 2.146715ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T14:19:48Z"
kind: List
metadata:
  resourceVersion: ""