apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 56eaf839-3f09-4ee5-9e83-7720a9ee6f75
    resourceVersion: "23954"
    uid: 5655b9cc-8bb1-45fd-9cab-6e36473ad066
  spec:
    sourcePod: network-check-source-989f8b8dc-94v5l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:23:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.883214ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:30:13Z"
    - latency: 987.1µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:29:13Z"
    - latency: 947.542µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:28:13Z"
    - latency: 1.597984ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:27:13Z"
    - latency: 1.198697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:26:13Z"
    - latency: 947.751µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:25:13Z"
    - latency: 1.103283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:24:13Z"
    - latency: 1.492144ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:23:13Z"
    - latency: 1.035878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:22:13Z"
    - latency: 1.241642ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:21:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 56eaf839-3f09-4ee5-9e83-7720a9ee6f75
    resourceVersion: "22808"
    uid: 16bf524e-fbb7-4928-af1f-f74c2c53ed1c
  spec:
    sourcePod: network-check-source-989f8b8dc-94v5l
    targetEndpoint: a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:22:13Z"
      message: 'load-balancer-api-external: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.528375ms
      message: 'load-balancer-api-external: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:28:13Z"
    - latency: 8.773029ms
      message: 'load-balancer-api-external: resolved host name a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:28:13Z"
    - latency: 5.91118ms
      message: 'load-balancer-api-external: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:27:13Z"
    - latency: 15.450401ms
      message: 'load-balancer-api-external: resolved host name a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:27:13Z"
    - latency: 6.104485ms
      message: 'load-balancer-api-external: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:26:13Z"
    - latency: 8.82503ms
      message: 'load-balancer-api-external: resolved host name a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:26:13Z"
    - latency: 5.212481ms
      message: 'load-balancer-api-external: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:25:13Z"
    - latency: 8.76679ms
      message: 'load-balancer-api-external: resolved host name a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:25:13Z"
    - latency: 5.523007ms
      message: 'load-balancer-api-external: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:24:13Z"
    - latency: 8.283141ms
      message: 'load-balancer-api-external: resolved host name a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:24:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 56eaf839-3f09-4ee5-9e83-7720a9ee6f75
    resourceVersion: "22807"
    uid: 5cd9f675-6c41-48f6-a0a5-23d44f1e5e41
  spec:
    sourcePod: network-check-source-989f8b8dc-94v5l
    targetEndpoint: a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:22:13Z"
      message: 'load-balancer-api-internal: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.476041ms
      message: 'load-balancer-api-internal: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:28:13Z"
    - latency: 8.645266ms
      message: 'load-balancer-api-internal: resolved host name a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:28:13Z"
    - latency: 4.79305ms
      message: 'load-balancer-api-internal: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:27:13Z"
    - latency: 15.482841ms
      message: 'load-balancer-api-internal: resolved host name a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:27:13Z"
    - latency: 6.055363ms
      message: 'load-balancer-api-internal: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:26:13Z"
    - latency: 8.689311ms
      message: 'load-balancer-api-internal: resolved host name a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:26:13Z"
    - latency: 5.18215ms
      message: 'load-balancer-api-internal: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:25:13Z"
    - latency: 8.788596ms
      message: 'load-balancer-api-internal: resolved host name a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:25:13Z"
    - latency: 5.53288ms
      message: 'load-balancer-api-internal: tcp connection to a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:24:13Z"
    - latency: 8.210557ms
      message: 'load-balancer-api-internal: resolved host name a8419a7700b244ecd950e859566cd826-cc0548a2ff1e8800.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:24:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-network-check-target-ip-10-0-132-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 56eaf839-3f09-4ee5-9e83-7720a9ee6f75
    resourceVersion: "23951"
    uid: e146e056-f119-42cd-9ec3-215ae3227314
  spec:
    sourcePod: network-check-source-989f8b8dc-94v5l
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:23:13Z"
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.431µs
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:30:13Z"
    - latency: 1.951143ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:29:13Z"
    - latency: 976.545µs
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:28:13Z"
    - latency: 1.848613ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:27:13Z"
    - latency: 912.251µs
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:26:13Z"
    - latency: 1.332315ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:25:13Z"
    - latency: 1.045836ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:24:13Z"
    - latency: 1.750995ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:23:13Z"
    - latency: 1.593552ms
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:22:13Z"
    - latency: 956.238µs
      message: 'network-check-target-ip-10-0-132-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:21:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-network-check-target-ip-10-0-132-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 56eaf839-3f09-4ee5-9e83-7720a9ee6f75
    resourceVersion: "23953"
    uid: 99b91d1e-5722-407b-b9e3-70fbb4df38e4
  spec:
    sourcePod: network-check-source-989f8b8dc-94v5l
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:23:13Z"
      message: 'network-check-target-ip-10-0-132-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.41265ms
      message: 'network-check-target-ip-10-0-132-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:30:13Z"
    - latency: 2.273709ms
      message: 'network-check-target-ip-10-0-132-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:29:13Z"
    - latency: 2.258933ms
      message: 'network-check-target-ip-10-0-132-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:28:13Z"
    - latency: 2.483474ms
      message: 'network-check-target-ip-10-0-132-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:27:13Z"
    - latency: 2.197076ms
      message: 'network-check-target-ip-10-0-132-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:26:13Z"
    - latency: 2.288937ms
      message: 'network-check-target-ip-10-0-132-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:25:13Z"
    - latency: 2.211525ms
      message: 'network-check-target-ip-10-0-132-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:24:13Z"
    - latency: 2.282694ms
      message: 'network-check-target-ip-10-0-132-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:23:13Z"
    - latency: 2.118372ms
      message: 'network-check-target-ip-10-0-132-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:22:13Z"
    - latency: 2.294343ms
      message: 'network-check-target-ip-10-0-132-60: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:21:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-network-check-target-ip-10-0-133-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 56eaf839-3f09-4ee5-9e83-7720a9ee6f75
    resourceVersion: "23952"
    uid: 97964caa-d4c2-402e-91cf-2edf69d7307b
  spec:
    sourcePod: network-check-source-989f8b8dc-94v5l
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:23:13Z"
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.02046ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:30:13Z"
    - latency: 2.257298ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:29:13Z"
    - latency: 2.345164ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:28:13Z"
    - latency: 2.457886ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:27:13Z"
    - latency: 2.22719ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:26:13Z"
    - latency: 2.028545ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:25:13Z"
    - latency: 2.246865ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:24:13Z"
    - latency: 2.187255ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:23:13Z"
    - latency: 2.392495ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:22:13Z"
    - latency: 2.068499ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:21:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-12-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-12.ec2.internal
      uid: 56eaf839-3f09-4ee5-9e83-7720a9ee6f75
    resourceVersion: "22806"
    uid: e7c25ead-efcf-418f-961b-ea559a4c8000
  spec:
    sourcePod: network-check-source-989f8b8dc-94v5l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:22:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.058785ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:28:13Z"
    - latency: 1.938117ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:28:13Z"
    - latency: 1.28917ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:27:13Z"
    - latency: 1.952784ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:27:13Z"
    - latency: 786.347µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:26:13Z"
    - latency: 2.343738ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:26:13Z"
    - latency: 972.808µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:25:13Z"
    - latency: 1.989351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:25:13Z"
    - latency: 1.174015ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:24:13Z"
    - latency: 1.926625ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:24:13Z"
kind: List
metadata:
  resourceVersion: ""