apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T01:56:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 9663c86f-fa1c-44e9-87e9-19cf81b445e2
    resourceVersion: "69226"
    uid: b206e432-9e14-4ee5-8121-2c2400e555a8
  spec:
    sourcePod: network-check-source-7cbc45fddc-q2gls
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T02:03:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.768µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:31:42Z"
    - latency: 917.651µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:30:42Z"
    - latency: 1.133088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:29:42Z"
    - latency: 1.01142ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:28:42Z"
    - latency: 1.100318ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:27:42Z"
    - latency: 840.273µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:26:42Z"
    - latency: 1.823555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:25:42Z"
    - latency: 1.261957ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:24:42Z"
    - latency: 873.45µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:23:42Z"
    - latency: 1.05146ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:22:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T01:56:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 9663c86f-fa1c-44e9-87e9-19cf81b445e2
    resourceVersion: "70094"
    uid: 4174c280-d988-4d9e-a107-c6f245320ac9
  spec:
    sourcePod: network-check-source-7cbc45fddc-q2gls
    targetEndpoint: af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T02:02:42Z"
      message: 'load-balancer-api-external: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.887325ms
      message: 'load-balancer-api-external: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:32:42Z"
    - latency: 8.46408ms
      message: 'load-balancer-api-external: resolved host name af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:32:42Z"
    - latency: 4.209114ms
      message: 'load-balancer-api-external: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:31:42Z"
    - latency: 10.758669ms
      message: 'load-balancer-api-external: resolved host name af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:31:42Z"
    - latency: 4.628242ms
      message: 'load-balancer-api-external: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:30:42Z"
    - latency: 9.120367ms
      message: 'load-balancer-api-external: resolved host name af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:30:42Z"
    - latency: 3.954757ms
      message: 'load-balancer-api-external: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:29:42Z"
    - latency: 8.917358ms
      message: 'load-balancer-api-external: resolved host name af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:29:42Z"
    - latency: 4.687782ms
      message: 'load-balancer-api-external: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:28:42Z"
    - latency: 6.939557ms
      message: 'load-balancer-api-external: resolved host name af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:28:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T01:56:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 9663c86f-fa1c-44e9-87e9-19cf81b445e2
    resourceVersion: "70095"
    uid: 0af95112-f5d1-40bf-be9b-4f249fbba0ec
  spec:
    sourcePod: network-check-source-7cbc45fddc-q2gls
    targetEndpoint: af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T02:02:42Z"
      message: 'load-balancer-api-internal: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.87557ms
      message: 'load-balancer-api-internal: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:32:42Z"
    - latency: 8.489974ms
      message: 'load-balancer-api-internal: resolved host name af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:32:42Z"
    - latency: 4.217378ms
      message: 'load-balancer-api-internal: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:31:42Z"
    - latency: 10.803658ms
      message: 'load-balancer-api-internal: resolved host name af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:31:42Z"
    - latency: 4.719813ms
      message: 'load-balancer-api-internal: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:30:42Z"
    - latency: 9.089565ms
      message: 'load-balancer-api-internal: resolved host name af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:30:42Z"
    - latency: 3.978288ms
      message: 'load-balancer-api-internal: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:29:42Z"
    - latency: 8.821627ms
      message: 'load-balancer-api-internal: resolved host name af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:29:42Z"
    - latency: 5.144223ms
      message: 'load-balancer-api-internal: tcp connection to af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:28:42Z"
    - latency: 6.963453ms
      message: 'load-balancer-api-internal: resolved host name af883d7203b874f24ad919c5751b982c-f3bca8403140f89d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:28:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T01:56:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-network-check-target-ip-10-0-130-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 9663c86f-fa1c-44e9-87e9-19cf81b445e2
    resourceVersion: "69224"
    uid: 60e9a3c5-bbba-4708-94e0-21169874c76d
  spec:
    sourcePod: network-check-source-7cbc45fddc-q2gls
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T02:03:42Z"
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.152941ms
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:31:42Z"
    - latency: 839.093µs
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:30:42Z"
    - latency: 855.645µs
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:29:42Z"
    - latency: 990.927µs
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:28:42Z"
    - latency: 1.073897ms
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:27:42Z"
    - latency: 1.055717ms
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:26:42Z"
    - latency: 2.784264ms
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:25:42Z"
    - latency: 1.211559ms
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:24:42Z"
    - latency: 1.271087ms
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:23:42Z"
    - latency: 959.528µs
      message: 'network-check-target-ip-10-0-130-159: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:22:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T01:56:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-network-check-target-ip-10-0-135-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 9663c86f-fa1c-44e9-87e9-19cf81b445e2
    resourceVersion: "69223"
    uid: e2488fbf-931c-4c7a-a712-dc9c4f804ad0
  spec:
    sourcePod: network-check-source-7cbc45fddc-q2gls
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T02:03:42Z"
      message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.247209ms
      message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:31:42Z"
    - latency: 2.40552ms
      message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:30:42Z"
    - latency: 2.183461ms
      message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:29:42Z"
    - latency: 2.122132ms
      message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:28:42Z"
    - latency: 2.259687ms
      message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:27:42Z"
    - latency: 2.345007ms
      message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:26:42Z"
    - latency: 2.516511ms
      message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:25:42Z"
    - latency: 2.384615ms
      message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:24:42Z"
    - latency: 2.35802ms
      message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:23:42Z"
    - latency: 2.350871ms
      message: 'network-check-target-ip-10-0-135-222: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:22:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T01:56:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-network-check-target-ip-10-0-137-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 9663c86f-fa1c-44e9-87e9-19cf81b445e2
    resourceVersion: "69225"
    uid: b61cd1d3-5fb9-4a7a-bd40-b6181fff7d41
  spec:
    sourcePod: network-check-source-7cbc45fddc-q2gls
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T02:03:42Z"
      message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.334644ms
      message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:31:42Z"
    - latency: 2.264376ms
      message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:30:42Z"
    - latency: 2.002616ms
      message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:29:42Z"
    - latency: 2.436146ms
      message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:28:42Z"
    - latency: 2.34572ms
      message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:27:42Z"
    - latency: 2.434915ms
      message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:26:42Z"
    - latency: 2.481588ms
      message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:25:42Z"
    - latency: 2.385897ms
      message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:24:42Z"
    - latency: 2.578599ms
      message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:23:42Z"
    - latency: 2.457533ms
      message: 'network-check-target-ip-10-0-137-50: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:22:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-20T01:56:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-159-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-159.ec2.internal
      uid: 9663c86f-fa1c-44e9-87e9-19cf81b445e2
    resourceVersion: "70093"
    uid: 95312aad-216d-4582-94eb-6ab962894510
  spec:
    sourcePod: network-check-source-7cbc45fddc-q2gls
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-20T02:02:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.174516ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:32:42Z"
    - latency: 2.319455ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:32:42Z"
    - latency: 936.022µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:31:42Z"
    - latency: 2.177256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:31:42Z"
    - latency: 1.07012ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:30:42Z"
    - latency: 1.793999ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:30:42Z"
    - latency: 1.072649ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:29:42Z"
    - latency: 2.028062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:29:42Z"
    - latency: 1.022595ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-20T02:28:42Z"
    - latency: 2.290577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-20T02:28:42Z"
kind: List
metadata:
  resourceVersion: ""