apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:20:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-199-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-199.ec2.internal
      uid: 747b6f24-b487-4319-bde2-6f8d57cfe411
    resourceVersion: "71431"
    uid: 3f4b757e-a9ed-45d4-b9cc-701111f7733e
  spec:
    sourcePod: network-check-source-7d88cb55d8-dkwmb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:27:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.156177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:09:36Z"
    - latency: 1.260737ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:08:36Z"
    - latency: 1.566573ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:07:36Z"
    - latency: 1.248836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:06:36Z"
    - latency: 1.145716ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:05:36Z"
    - latency: 1.138941ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:04:36Z"
    - latency: 1.165759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:03:36Z"
    - latency: 908.628µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:02:36Z"
    - latency: 1.389093ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:01:36Z"
    - latency: 1.695813ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:00:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:20:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-199-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-199.ec2.internal
      uid: 747b6f24-b487-4319-bde2-6f8d57cfe411
    resourceVersion: "69329"
    uid: 9a6a1e6b-ab5d-4a99-b31e-803ac43125d4
  spec:
    sourcePod: network-check-source-7d88cb55d8-dkwmb
    targetEndpoint: a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:26:36Z"
      message: 'load-balancer-api-external: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.93301ms
      message: 'load-balancer-api-external: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:08:36Z"
    - latency: 9.432294ms
      message: 'load-balancer-api-external: resolved host name a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:08:36Z"
    - latency: 3.043974ms
      message: 'load-balancer-api-external: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:07:36Z"
    - latency: 9.448472ms
      message: 'load-balancer-api-external: resolved host name a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:07:36Z"
    - latency: 5.929145ms
      message: 'load-balancer-api-external: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:06:36Z"
    - latency: 10.137402ms
      message: 'load-balancer-api-external: resolved host name a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:06:36Z"
    - latency: 4.361023ms
      message: 'load-balancer-api-external: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:05:36Z"
    - latency: 7.208538ms
      message: 'load-balancer-api-external: resolved host name a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:05:36Z"
    - latency: 2.777967ms
      message: 'load-balancer-api-external: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:04:36Z"
    - latency: 6.803797ms
      message: 'load-balancer-api-external: resolved host name a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:04:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:20:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-199-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-199.ec2.internal
      uid: 747b6f24-b487-4319-bde2-6f8d57cfe411
    resourceVersion: "69330"
    uid: f23605e1-02cd-4f24-b382-9f1cfd57d1ba
  spec:
    sourcePod: network-check-source-7d88cb55d8-dkwmb
    targetEndpoint: a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:26:36Z"
      message: 'load-balancer-api-internal: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.935988ms
      message: 'load-balancer-api-internal: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:08:36Z"
    - latency: 9.46756ms
      message: 'load-balancer-api-internal: resolved host name a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:08:36Z"
    - latency: 5.682725ms
      message: 'load-balancer-api-internal: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:07:36Z"
    - latency: 9.295375ms
      message: 'load-balancer-api-internal: resolved host name a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:07:36Z"
    - latency: 5.346001ms
      message: 'load-balancer-api-internal: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:06:36Z"
    - latency: 10.172071ms
      message: 'load-balancer-api-internal: resolved host name a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:06:36Z"
    - latency: 4.367808ms
      message: 'load-balancer-api-internal: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:05:36Z"
    - latency: 7.259167ms
      message: 'load-balancer-api-internal: resolved host name a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:05:36Z"
    - latency: 3.482015ms
      message: 'load-balancer-api-internal: tcp connection to a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:04:36Z"
    - latency: 6.853952ms
      message: 'load-balancer-api-internal: resolved host name a5d7aa105bd984da499ab94f6cad240b-c5bc135e21979031.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:04:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-199-to-network-check-target-ip-10-0-129-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-199.ec2.internal
      uid: 747b6f24-b487-4319-bde2-6f8d57cfe411
    resourceVersion: "71430"
    uid: 8ee1d2b7-d8a6-4ca4-adfb-0ce0d207967f
  spec:
    sourcePod: network-check-source-7d88cb55d8-dkwmb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:27:36Z"
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.185949ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:09:36Z"
    - latency: 2.292478ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:08:36Z"
    - latency: 2.083737ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:07:36Z"
    - latency: 1.959462ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:06:36Z"
    - latency: 2.249412ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:05:36Z"
    - latency: 2.135847ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:04:36Z"
    - latency: 2.216195ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:03:36Z"
    - latency: 1.917962ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:02:36Z"
    - latency: 1.814897ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:01:36Z"
    - latency: 2.018535ms
      message: 'network-check-target-ip-10-0-129-154: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:00:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-199-to-network-check-target-ip-10-0-135-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-199.ec2.internal
      uid: 747b6f24-b487-4319-bde2-6f8d57cfe411
    resourceVersion: "71429"
    uid: 80365be3-7c61-4f67-ba61-847b434fa685
  spec:
    sourcePod: network-check-source-7d88cb55d8-dkwmb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:27:36Z"
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.303796ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:09:36Z"
    - latency: 2.250394ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:08:36Z"
    - latency: 2.262393ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:07:36Z"
    - latency: 2.394663ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:06:36Z"
    - latency: 2.396523ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:05:36Z"
    - latency: 2.163077ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:04:36Z"
    - latency: 2.207161ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:03:36Z"
    - latency: 2.41692ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:02:36Z"
    - latency: 2.0608ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:01:36Z"
    - latency: 2.020269ms
      message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:00:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:20:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-199-to-network-check-target-ip-10-0-140-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-199.ec2.internal
      uid: 747b6f24-b487-4319-bde2-6f8d57cfe411
    resourceVersion: "71428"
    uid: e438e572-09ee-4413-8554-205c6c7a5231
  spec:
    sourcePod: network-check-source-7d88cb55d8-dkwmb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:27:36Z"
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.681µs
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:09:36Z"
    - latency: 806.884µs
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:08:36Z"
    - latency: 911.734µs
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:07:36Z"
    - latency: 966.011µs
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:06:36Z"
    - latency: 1.453246ms
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:05:36Z"
    - latency: 917.088µs
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:04:36Z"
    - latency: 936.195µs
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:03:36Z"
    - latency: 943.585µs
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:02:36Z"
    - latency: 747.769µs
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:01:36Z"
    - latency: 847.68µs
      message: 'network-check-target-ip-10-0-140-199: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:00:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T16:20:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-199-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-199.ec2.internal
      uid: 747b6f24-b487-4319-bde2-6f8d57cfe411
    resourceVersion: "69328"
    uid: cc26f284-299a-4ce1-8844-322458dbd2bb
  spec:
    sourcePod: network-check-source-7d88cb55d8-dkwmb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T16:26:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.201µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:08:36Z"
    - latency: 2.675721ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:08:36Z"
    - latency: 780.725µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:07:36Z"
    - latency: 2.280788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:07:36Z"
    - latency: 997.291µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:06:36Z"
    - latency: 1.931189ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:06:36Z"
    - latency: 890.909µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:05:36Z"
    - latency: 1.889272ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:05:36Z"
    - latency: 987.464µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T17:04:36Z"
    - latency: 1.919982ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T17:04:36Z"
kind: List
metadata:
  resourceVersion: ""