apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:01:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-139-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-139.ec2.internal
      uid: 8f0b90e5-aced-417f-921c-f092f0bad366
    resourceVersion: "54828"
    uid: 3fe17d4c-2ea6-43ae-a134-5c59a7cbb2d7
  spec:
    sourcePod: network-check-source-989f8b8dc-x44jg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:08:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 973.576µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:36:40Z"
    - latency: 1.102864ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:35:40Z"
    - latency: 1.083524ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:40Z"
    - latency: 1.617379ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:40Z"
    - latency: 993.485µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:32:40Z"
    - latency: 1.345183ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:31:40Z"
    - latency: 969.731µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:30:40Z"
    - latency: 835.482µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:29:40Z"
    - latency: 876.621µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:28:40Z"
    - latency: 961.978µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:27:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:01:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-139-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-139.ec2.internal
      uid: 8f0b90e5-aced-417f-921c-f092f0bad366
    resourceVersion: "55736"
    uid: dc4f3fe7-f301-4534-b375-7c7d9871ea42
  spec:
    sourcePod: network-check-source-989f8b8dc-x44jg
    targetEndpoint: aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:07:40Z"
      message: 'load-balancer-api-external: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.160697ms
      message: 'load-balancer-api-external: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:37:40Z"
    - latency: 7.807968ms
      message: 'load-balancer-api-external: resolved host name aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:37:40Z"
    - latency: 5.335094ms
      message: 'load-balancer-api-external: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:36:40Z"
    - latency: 8.294526ms
      message: 'load-balancer-api-external: resolved host name aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:36:40Z"
    - latency: 5.639444ms
      message: 'load-balancer-api-external: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:35:40Z"
    - latency: 8.366562ms
      message: 'load-balancer-api-external: resolved host name aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:35:40Z"
    - latency: 3.960965ms
      message: 'load-balancer-api-external: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:40Z"
    - latency: 8.059845ms
      message: 'load-balancer-api-external: resolved host name aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:34:40Z"
    - latency: 5.098167ms
      message: 'load-balancer-api-external: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:40Z"
    - latency: 8.3669ms
      message: 'load-balancer-api-external: resolved host name aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:33:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:01:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-139-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-139.ec2.internal
      uid: 8f0b90e5-aced-417f-921c-f092f0bad366
    resourceVersion: "55735"
    uid: dca73807-ef18-4b62-8861-20bdb0fbf6bc
  spec:
    sourcePod: network-check-source-989f8b8dc-x44jg
    targetEndpoint: aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:07:40Z"
      message: 'load-balancer-api-internal: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.186944ms
      message: 'load-balancer-api-internal: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:37:40Z"
    - latency: 7.799772ms
      message: 'load-balancer-api-internal: resolved host name aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:37:40Z"
    - latency: 5.367163ms
      message: 'load-balancer-api-internal: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:36:40Z"
    - latency: 8.166712ms
      message: 'load-balancer-api-internal: resolved host name aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:36:40Z"
    - latency: 5.674431ms
      message: 'load-balancer-api-internal: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:35:40Z"
    - latency: 8.544375ms
      message: 'load-balancer-api-internal: resolved host name aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:35:40Z"
    - latency: 5.266226ms
      message: 'load-balancer-api-internal: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:40Z"
    - latency: 7.962966ms
      message: 'load-balancer-api-internal: resolved host name aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:34:40Z"
    - latency: 5.081556ms
      message: 'load-balancer-api-internal: tcp connection to aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:40Z"
    - latency: 8.428448ms
      message: 'load-balancer-api-internal: resolved host name aac833873376e4edc866b1bb4f45d0a1-6d0b6bef25435147.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:33:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:01:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-139-to-network-check-target-ip-10-0-130-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-139.ec2.internal
      uid: 8f0b90e5-aced-417f-921c-f092f0bad366
    resourceVersion: "54827"
    uid: af01f9db-16fe-4bbe-a1c0-09435f8d9a1e
  spec:
    sourcePod: network-check-source-989f8b8dc-x44jg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:08:40Z"
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.253104ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:36:40Z"
    - latency: 2.436995ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:35:40Z"
    - latency: 2.302485ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:40Z"
    - latency: 3.063162ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:40Z"
    - latency: 2.291272ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:32:40Z"
    - latency: 2.374509ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:31:40Z"
    - latency: 2.562387ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:30:40Z"
    - latency: 2.220997ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:29:40Z"
    - latency: 2.176308ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:28:40Z"
    - latency: 2.45616ms
      message: 'network-check-target-ip-10-0-130-52: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:27:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:01:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-139-to-network-check-target-ip-10-0-133-139
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-139.ec2.internal
      uid: 8f0b90e5-aced-417f-921c-f092f0bad366
    resourceVersion: "54825"
    uid: 64790c41-a272-4e60-910c-9932e0799911
  spec:
    sourcePod: network-check-source-989f8b8dc-x44jg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:08:40Z"
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.69µs
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:36:40Z"
    - latency: 846.779µs
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:35:40Z"
    - latency: 852.522µs
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:40Z"
    - latency: 856.328µs
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:40Z"
    - latency: 811.213µs
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:32:40Z"
    - latency: 1.314188ms
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:31:40Z"
    - latency: 940.063µs
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:30:40Z"
    - latency: 832.086µs
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:29:40Z"
    - latency: 899.955µs
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:28:40Z"
    - latency: 801.416µs
      message: 'network-check-target-ip-10-0-133-139: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:27:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:01:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-139-to-network-check-target-ip-10-0-142-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-139.ec2.internal
      uid: 8f0b90e5-aced-417f-921c-f092f0bad366
    resourceVersion: "54826"
    uid: 89c54c7f-da6c-4c58-a674-5e4bf3bdb786
  spec:
    sourcePod: network-check-source-989f8b8dc-x44jg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:08:40Z"
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.2439ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:36:40Z"
    - latency: 2.298976ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:35:40Z"
    - latency: 2.419903ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:40Z"
    - latency: 2.103694ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:40Z"
    - latency: 2.34366ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:32:40Z"
    - latency: 2.587226ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:31:40Z"
    - latency: 2.339675ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:30:40Z"
    - latency: 2.62729ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:29:40Z"
    - latency: 2.150669ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:28:40Z"
    - latency: 2.263354ms
      message: 'network-check-target-ip-10-0-142-92: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:27:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T00:01:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-139-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-139.ec2.internal
      uid: 8f0b90e5-aced-417f-921c-f092f0bad366
    resourceVersion: "55734"
    uid: 5afbc207-46b9-4397-b6ae-bec3bb3e9a5c
  spec:
    sourcePod: network-check-source-989f8b8dc-x44jg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T00:07:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.186µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:37:40Z"
    - latency: 1.812745ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:37:40Z"
    - latency: 858.542µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:36:40Z"
    - latency: 1.616432ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:36:40Z"
    - latency: 887.39µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:35:40Z"
    - latency: 1.77389ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:35:40Z"
    - latency: 1.203912ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:34:40Z"
    - latency: 1.744438ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:34:40Z"
    - latency: 1.692075ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T00:33:40Z"
    - latency: 1.750512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T00:33:40Z"
kind: List
metadata:
  resourceVersion: ""