apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T20:04:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 85d3588f-f05c-47aa-bcbd-762316836324
    resourceVersion: "67938"
    uid: 6e532189-6a00-4247-9264-46a07b9842a6
  spec:
    sourcePod: network-check-source-6f8b768455-r4f5p
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T20:11:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.103866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:39:29Z"
    - latency: 850.3µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:38:29Z"
    - latency: 990.165µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:37:29Z"
    - latency: 955.952µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:36:29Z"
    - latency: 1.136818ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:35:29Z"
    - latency: 1.510449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:34:29Z"
    - latency: 1.215974ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:33:29Z"
    - latency: 1.368588ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:32:29Z"
    - latency: 879.366µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:31:29Z"
    - latency: 1.452535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:30:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T20:04:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 85d3588f-f05c-47aa-bcbd-762316836324
    resourceVersion: "68859"
    uid: 13a4f1a7-2df5-41d1-9bef-631dfba09e1c
  spec:
    sourcePod: network-check-source-6f8b768455-r4f5p
    targetEndpoint: afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T20:10:29Z"
      message: 'load-balancer-api-external: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.68257ms
      message: 'load-balancer-api-external: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:40:29Z"
    - latency: 8.731884ms
      message: 'load-balancer-api-external: resolved host name afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:40:29Z"
    - latency: 3.992127ms
      message: 'load-balancer-api-external: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:39:29Z"
    - latency: 9.686053ms
      message: 'load-balancer-api-external: resolved host name afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:39:29Z"
    - latency: 4.894072ms
      message: 'load-balancer-api-external: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:38:29Z"
    - latency: 8.55701ms
      message: 'load-balancer-api-external: resolved host name afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:38:29Z"
    - latency: 5.326152ms
      message: 'load-balancer-api-external: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:37:29Z"
    - latency: 8.176498ms
      message: 'load-balancer-api-external: resolved host name afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:37:29Z"
    - latency: 3.72237ms
      message: 'load-balancer-api-external: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:36:29Z"
    - latency: 8.59508ms
      message: 'load-balancer-api-external: resolved host name afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:36:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T20:04:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 85d3588f-f05c-47aa-bcbd-762316836324
    resourceVersion: "68858"
    uid: 7ba6f147-fe2a-455a-b095-0529772d912e
  spec:
    sourcePod: network-check-source-6f8b768455-r4f5p
    targetEndpoint: afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T20:10:29Z"
      message: 'load-balancer-api-internal: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.695316ms
      message: 'load-balancer-api-internal: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:40:29Z"
    - latency: 8.761061ms
      message: 'load-balancer-api-internal: resolved host name afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:40:29Z"
    - latency: 4.003403ms
      message: 'load-balancer-api-internal: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:39:29Z"
    - latency: 9.804625ms
      message: 'load-balancer-api-internal: resolved host name afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:39:29Z"
    - latency: 5.276674ms
      message: 'load-balancer-api-internal: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:38:29Z"
    - latency: 8.576712ms
      message: 'load-balancer-api-internal: resolved host name afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:38:29Z"
    - latency: 5.311684ms
      message: 'load-balancer-api-internal: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:37:29Z"
    - latency: 8.225005ms
      message: 'load-balancer-api-internal: resolved host name afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:37:29Z"
    - latency: 3.570283ms
      message: 'load-balancer-api-internal: tcp connection to afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:36:29Z"
    - latency: 8.638068ms
      message: 'load-balancer-api-internal: resolved host name afa44a826e27a4b1b97ca671fea31d39-6a16838da6fafbf0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:36:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T20:04:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-network-check-target-ip-10-0-128-209
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 85d3588f-f05c-47aa-bcbd-762316836324
    resourceVersion: "67935"
    uid: e9209e45-ca53-441a-a532-8f4247b6356e
  spec:
    sourcePod: network-check-source-6f8b768455-r4f5p
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T20:11:29Z"
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.577374ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:39:29Z"
    - latency: 1.925555ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:38:29Z"
    - latency: 1.904576ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:37:29Z"
    - latency: 2.231711ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:36:29Z"
    - latency: 2.186439ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:35:29Z"
    - latency: 2.29702ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:34:29Z"
    - latency: 2.191988ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:33:29Z"
    - latency: 2.386936ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:32:29Z"
    - latency: 2.073289ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:31:29Z"
    - latency: 2.174535ms
      message: 'network-check-target-ip-10-0-128-209: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:30:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T20:04:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-network-check-target-ip-10-0-130-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 85d3588f-f05c-47aa-bcbd-762316836324
    resourceVersion: "67934"
    uid: fc020542-b54f-441e-9a3e-c8ccef6810bc
  spec:
    sourcePod: network-check-source-6f8b768455-r4f5p
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T20:11:29Z"
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 915.393µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:39:29Z"
    - latency: 1.250431ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:38:29Z"
    - latency: 919.019µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:37:29Z"
    - latency: 859.578µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:36:29Z"
    - latency: 831.655µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:35:29Z"
    - latency: 928.444µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:34:29Z"
    - latency: 1.265309ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:33:29Z"
    - latency: 974.083µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:32:29Z"
    - latency: 860.552µs
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:31:29Z"
    - latency: 1.531932ms
      message: 'network-check-target-ip-10-0-130-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:30:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T20:04:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-network-check-target-ip-10-0-138-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 85d3588f-f05c-47aa-bcbd-762316836324
    resourceVersion: "67936"
    uid: 200b08d5-b341-4555-88cb-204b5b4a76ca
  spec:
    sourcePod: network-check-source-6f8b768455-r4f5p
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T20:11:29Z"
      message: 'network-check-target-ip-10-0-138-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.420129ms
      message: 'network-check-target-ip-10-0-138-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:39:29Z"
    - latency: 1.76904ms
      message: 'network-check-target-ip-10-0-138-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:38:29Z"
    - latency: 2.016278ms
      message: 'network-check-target-ip-10-0-138-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:37:29Z"
    - latency: 1.992394ms
      message: 'network-check-target-ip-10-0-138-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:36:29Z"
    - latency: 1.86349ms
      message: 'network-check-target-ip-10-0-138-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:35:29Z"
    - latency: 3.114538ms
      message: 'network-check-target-ip-10-0-138-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:34:29Z"
    - latency: 2.108241ms
      message: 'network-check-target-ip-10-0-138-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:33:29Z"
    - latency: 2.647253ms
      message: 'network-check-target-ip-10-0-138-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:32:29Z"
    - latency: 2.321151ms
      message: 'network-check-target-ip-10-0-138-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:31:29Z"
    - latency: 2.085452ms
      message: 'network-check-target-ip-10-0-138-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:30:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T20:04:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-146.ec2.internal
      uid: 85d3588f-f05c-47aa-bcbd-762316836324
    resourceVersion: "68857"
    uid: 6992f14f-d982-4ecb-8e36-7119415f4e55
  spec:
    sourcePod: network-check-source-6f8b768455-r4f5p
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T20:10:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 856.87µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:40:29Z"
    - latency: 1.733334ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:40:29Z"
    - latency: 1.06613ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:39:29Z"
    - latency: 1.75354ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:39:29Z"
    - latency: 991.81µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:38:29Z"
    - latency: 1.832174ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:38:29Z"
    - latency: 805.709µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:37:29Z"
    - latency: 1.91154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:37:29Z"
    - latency: 1.081149ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T20:36:29Z"
    - latency: 1.751595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T20:36:29Z"
kind: List
metadata:
  resourceVersion: ""