apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:56:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 7fc447a6-8f38-4681-a49f-b6e08a1251d8
    resourceVersion: "55539"
    uid: e0687c43-7ce9-48d4-bbbc-ffb7940d81f3
  spec:
    sourcePod: network-check-source-6f8b768455-mx52h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:03:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 917.192µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:24:16Z"
    - latency: 952.685µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:23:16Z"
    - latency: 967.448µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:22:16Z"
    - latency: 888.003µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:21:16Z"
    - latency: 1.209424ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:20:16Z"
    - latency: 1.24916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:19:16Z"
    - latency: 1.481094ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:18:16Z"
    - latency: 1.174331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:17:16Z"
    - latency: 1.450193ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:16:16Z"
    - latency: 1.018524ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:15:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:56:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 7fc447a6-8f38-4681-a49f-b6e08a1251d8
    resourceVersion: "56903"
    uid: ecc652a1-7b4f-41d0-95f3-7e452ac6048f
  spec:
    sourcePod: network-check-source-6f8b768455-mx52h
    targetEndpoint: a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:02:16Z"
      message: 'load-balancer-api-external: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.489264ms
      message: 'load-balancer-api-external: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:26:16Z"
    - latency: 8.033716ms
      message: 'load-balancer-api-external: resolved host name a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:26:16Z"
    - latency: 5.078006ms
      message: 'load-balancer-api-external: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:25:16Z"
    - latency: 7.724323ms
      message: 'load-balancer-api-external: resolved host name a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:25:16Z"
    - latency: 4.954797ms
      message: 'load-balancer-api-external: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:24:16Z"
    - latency: 8.359651ms
      message: 'load-balancer-api-external: resolved host name a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:24:16Z"
    - latency: 5.390578ms
      message: 'load-balancer-api-external: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:23:16Z"
    - latency: 9.318747ms
      message: 'load-balancer-api-external: resolved host name a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:23:16Z"
    - latency: 5.0897ms
      message: 'load-balancer-api-external: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:22:16Z"
    - latency: 9.712562ms
      message: 'load-balancer-api-external: resolved host name a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:22:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:56:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 7fc447a6-8f38-4681-a49f-b6e08a1251d8
    resourceVersion: "56904"
    uid: 53bfc71d-e5d0-4c35-ab5a-1fea7341047b
  spec:
    sourcePod: network-check-source-6f8b768455-mx52h
    targetEndpoint: a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:02:16Z"
      message: 'load-balancer-api-internal: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.510663ms
      message: 'load-balancer-api-internal: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:26:16Z"
    - latency: 8.054842ms
      message: 'load-balancer-api-internal: resolved host name a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:26:16Z"
    - latency: 5.418039ms
      message: 'load-balancer-api-internal: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:25:16Z"
    - latency: 7.777703ms
      message: 'load-balancer-api-internal: resolved host name a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:25:16Z"
    - latency: 6.504519ms
      message: 'load-balancer-api-internal: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:24:16Z"
    - latency: 8.249257ms
      message: 'load-balancer-api-internal: resolved host name a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:24:16Z"
    - latency: 5.320592ms
      message: 'load-balancer-api-internal: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:23:16Z"
    - latency: 9.447984ms
      message: 'load-balancer-api-internal: resolved host name a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:23:16Z"
    - latency: 5.126071ms
      message: 'load-balancer-api-internal: tcp connection to a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:22:16Z"
    - latency: 9.603523ms
      message: 'load-balancer-api-internal: resolved host name a6c0e9971c84345fda5d80fbba11de5d-ef3a480306a84f6b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:22:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:56:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-ip-10-0-128-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 7fc447a6-8f38-4681-a49f-b6e08a1251d8
    resourceVersion: "55537"
    uid: 2ad4dab1-713f-4de5-b331-79321adca54d
  spec:
    sourcePod: network-check-source-6f8b768455-mx52h
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:03:16Z"
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.11298ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:24:16Z"
    - latency: 2.349226ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:23:16Z"
    - latency: 2.759169ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:22:16Z"
    - latency: 2.546789ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:21:16Z"
    - latency: 2.614331ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:20:16Z"
    - latency: 2.306621ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:19:16Z"
    - latency: 2.583276ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:18:16Z"
    - latency: 2.583882ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:17:16Z"
    - latency: 2.380644ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:16:16Z"
    - latency: 2.192305ms
      message: 'network-check-target-ip-10-0-128-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:15:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:56:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-ip-10-0-128-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 7fc447a6-8f38-4681-a49f-b6e08a1251d8
    resourceVersion: "55538"
    uid: e205e428-057c-4b56-b858-a81d5506abac
  spec:
    sourcePod: network-check-source-6f8b768455-mx52h
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:03:16Z"
      message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.973106ms
      message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:24:16Z"
    - latency: 2.348397ms
      message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:23:16Z"
    - latency: 2.442967ms
      message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:22:16Z"
    - latency: 2.218424ms
      message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:21:16Z"
    - latency: 2.54407ms
      message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:20:16Z"
    - latency: 2.203985ms
      message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:19:16Z"
    - latency: 3.001422ms
      message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:18:16Z"
    - latency: 2.714261ms
      message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:17:16Z"
    - latency: 2.334053ms
      message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:16:16Z"
    - latency: 2.221591ms
      message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:15:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:56:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-ip-10-0-136-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 7fc447a6-8f38-4681-a49f-b6e08a1251d8
    resourceVersion: "55536"
    uid: 021f07aa-1e15-456e-a04d-d48e21a93271
  spec:
    sourcePod: network-check-source-6f8b768455-mx52h
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:03:16Z"
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.93µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:24:16Z"
    - latency: 931.45µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:23:16Z"
    - latency: 1.057924ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:22:16Z"
    - latency: 828.582µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:21:16Z"
    - latency: 1.05206ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:20:16Z"
    - latency: 957.993µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:19:16Z"
    - latency: 1.308245ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:18:16Z"
    - latency: 1.329665ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:17:16Z"
    - latency: 1.345346ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:16:16Z"
    - latency: 1.056635ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:15:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T13:56:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: 7fc447a6-8f38-4681-a49f-b6e08a1251d8
    resourceVersion: "56901"
    uid: c444c10b-7e3d-404c-8d57-3c32056f42d9
  spec:
    sourcePod: network-check-source-6f8b768455-mx52h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:02:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.090311ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:26:16Z"
    - latency: 1.840898ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:26:16Z"
    - latency: 972.355µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:25:16Z"
    - latency: 1.846445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:25:16Z"
    - latency: 1.028486ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:24:16Z"
    - latency: 1.800822ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:24:16Z"
    - latency: 839.22µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:23:16Z"
    - latency: 1.903407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:23:16Z"
    - latency: 832.091µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:22:16Z"
    - latency: 1.655958ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:22:16Z"
kind: List
metadata:
  resourceVersion: ""