apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:07:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-20-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-20.ec2.internal
      uid: 0392037e-449f-436a-8784-a2c26f9adba1
    resourceVersion: "67479"
    uid: 496c8791-9814-4000-9a07-f9db46b489dd
  spec:
    sourcePod: network-check-source-7cbc45fddc-xq5cn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:14:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.47µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:32Z"
    - latency: 1.108107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:32Z"
    - latency: 967.212µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:32Z"
    - latency: 1.002335ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:32Z"
    - latency: 1.444911ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:32Z"
    - latency: 1.131799ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:32Z"
    - latency: 1.296569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:32Z"
    - latency: 939.796µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:32Z"
    - latency: 1.359191ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:32Z"
    - latency: 1.421513ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:33:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:07:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-20-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-20.ec2.internal
      uid: 0392037e-449f-436a-8784-a2c26f9adba1
    resourceVersion: "63114"
    uid: 373a54f8-8803-4996-9a25-13af824bdc8f
  spec:
    sourcePod: network-check-source-7cbc45fddc-xq5cn
    targetEndpoint: ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:13:32Z"
      message: 'load-balancer-api-external: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.842132ms
      message: 'load-balancer-api-external: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:32Z"
    - latency: 8.217364ms
      message: 'load-balancer-api-external: resolved host name ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:32Z"
    - latency: 5.880243ms
      message: 'load-balancer-api-external: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:32Z"
    - latency: 7.647783ms
      message: 'load-balancer-api-external: resolved host name ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:36:32Z"
    - latency: 4.954494ms
      message: 'load-balancer-api-external: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:32Z"
    - latency: 12.720274ms
      message: 'load-balancer-api-external: resolved host name ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:35:32Z"
    - latency: 6.424565ms
      message: 'load-balancer-api-external: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:32Z"
    - latency: 7.714555ms
      message: 'load-balancer-api-external: resolved host name ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:34:32Z"
    - latency: 3.672228ms
      message: 'load-balancer-api-external: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:33:32Z"
    - latency: 6.926908ms
      message: 'load-balancer-api-external: resolved host name ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:33:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:07:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-20-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-20.ec2.internal
      uid: 0392037e-449f-436a-8784-a2c26f9adba1
    resourceVersion: "63115"
    uid: db707be9-e3d4-4a8f-acc7-7570ab0aa667
  spec:
    sourcePod: network-check-source-7cbc45fddc-xq5cn
    targetEndpoint: ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:13:32Z"
      message: 'load-balancer-api-internal: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.896352ms
      message: 'load-balancer-api-internal: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:32Z"
    - latency: 8.144808ms
      message: 'load-balancer-api-internal: resolved host name ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:32Z"
    - latency: 5.863586ms
      message: 'load-balancer-api-internal: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:32Z"
    - latency: 7.726908ms
      message: 'load-balancer-api-internal: resolved host name ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:36:32Z"
    - latency: 4.932691ms
      message: 'load-balancer-api-internal: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:32Z"
    - latency: 12.661363ms
      message: 'load-balancer-api-internal: resolved host name ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:35:32Z"
    - latency: 6.439044ms
      message: 'load-balancer-api-internal: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:32Z"
    - latency: 7.792098ms
      message: 'load-balancer-api-internal: resolved host name ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:34:32Z"
    - latency: 5.119816ms
      message: 'load-balancer-api-internal: tcp connection to ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:33:32Z"
    - latency: 7.010151ms
      message: 'load-balancer-api-internal: resolved host name ae26e3df5879c407486043d909141685-46ba9318f44ad85f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:33:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:07:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-20-to-network-check-target-ip-10-0-130-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-20.ec2.internal
      uid: 0392037e-449f-436a-8784-a2c26f9adba1
    resourceVersion: "67477"
    uid: 9059625e-a05c-463e-9e7c-e826523cc124
  spec:
    sourcePod: network-check-source-7cbc45fddc-xq5cn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:14:32Z"
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.48364ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:32Z"
    - latency: 2.85608ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:32Z"
    - latency: 2.116561ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:32Z"
    - latency: 2.311202ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:32Z"
    - latency: 2.482504ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:32Z"
    - latency: 2.435703ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:32Z"
    - latency: 2.376601ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:32Z"
    - latency: 2.432658ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:32Z"
    - latency: 2.432765ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:32Z"
    - latency: 2.478919ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:33:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:07:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-20-to-network-check-target-ip-10-0-131-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-20.ec2.internal
      uid: 0392037e-449f-436a-8784-a2c26f9adba1
    resourceVersion: "67474"
    uid: a7a295ae-0e25-4e04-8926-48ac1e13cd01
  spec:
    sourcePod: network-check-source-7cbc45fddc-xq5cn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:14:32Z"
      message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 962.655µs
      message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:32Z"
    - latency: 908.749µs
      message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:32Z"
    - latency: 942.816µs
      message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:32Z"
    - latency: 1.366693ms
      message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:32Z"
    - latency: 980.309µs
      message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:32Z"
    - latency: 1.056796ms
      message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:32Z"
    - latency: 981.526µs
      message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:32Z"
    - latency: 1.145089ms
      message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:32Z"
    - latency: 949.253µs
      message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:32Z"
    - latency: 1.550678ms
      message: 'network-check-target-ip-10-0-131-20: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:33:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:07:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-20-to-network-check-target-ip-10-0-135-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-20.ec2.internal
      uid: 0392037e-449f-436a-8784-a2c26f9adba1
    resourceVersion: "67476"
    uid: d8c2d0bc-3022-49a5-958d-0eaf64d3a7a2
  spec:
    sourcePod: network-check-source-7cbc45fddc-xq5cn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:14:32Z"
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.161647ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:42:32Z"
    - latency: 2.250947ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:41:32Z"
    - latency: 2.200698ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:40:32Z"
    - latency: 2.481336ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:39:32Z"
    - latency: 2.709174ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:38:32Z"
    - latency: 2.542802ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:32Z"
    - latency: 2.513672ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:32Z"
    - latency: 2.36739ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:32Z"
    - latency: 2.53021ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:32Z"
    - latency: 2.743411ms
      message: 'network-check-target-ip-10-0-135-232: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:33:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T20:07:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-20-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-20.ec2.internal
      uid: 0392037e-449f-436a-8784-a2c26f9adba1
    resourceVersion: "63113"
    uid: a278a18e-9c5c-4f0d-96ea-d8dab66a33a4
  spec:
    sourcePod: network-check-source-7cbc45fddc-xq5cn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T20:13:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030984ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:37:32Z"
    - latency: 1.961744ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:37:32Z"
    - latency: 1.14194ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:36:32Z"
    - latency: 1.878176ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:36:32Z"
    - latency: 1.272618ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:35:32Z"
    - latency: 2.041698ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:35:32Z"
    - latency: 1.376726ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:34:32Z"
    - latency: 1.954336ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:34:32Z"
    - latency: 1.635122ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:33:32Z"
    - latency: 2.028672ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:33:32Z"
kind: List
metadata:
  resourceVersion: ""