apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T19:04:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-11-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-11.ec2.internal
      uid: 9f638746-4fe3-4c07-b54b-55cb927f0019
    resourceVersion: "61879"
    uid: ef6e001d-1044-4028-bd6d-88ea41fce6c3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kzdhn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:11:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.071889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:46:17Z"
    - latency: 1.573671ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:45:17Z"
    - latency: 1.286206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:44:17Z"
    - latency: 1.266011ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:43:17Z"
    - latency: 912.02µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:42:17Z"
    - latency: 975.437µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:41:17Z"
    - latency: 1.183966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:40:17Z"
    - latency: 1.000102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:39:17Z"
    - latency: 1.18488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:38:17Z"
    - latency: 1.093351ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:37:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T19:04:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-11-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-11.ec2.internal
      uid: 9f638746-4fe3-4c07-b54b-55cb927f0019
    resourceVersion: "61880"
    uid: 670ca5e1-337e-4c30-b478-22d200ec208d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kzdhn
    targetEndpoint: a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:10:17Z"
      message: 'load-balancer-api-external: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.786929ms
      message: 'load-balancer-api-external: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:46:17Z"
    - latency: 6.818022ms
      message: 'load-balancer-api-external: resolved host name a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:46:17Z"
    - latency: 3.690278ms
      message: 'load-balancer-api-external: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:45:17Z"
    - latency: 6.617238ms
      message: 'load-balancer-api-external: resolved host name a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:45:17Z"
    - latency: 4.105397ms
      message: 'load-balancer-api-external: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:44:17Z"
    - latency: 7.451747ms
      message: 'load-balancer-api-external: resolved host name a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:44:17Z"
    - latency: 3.515493ms
      message: 'load-balancer-api-external: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:43:17Z"
    - latency: 6.730155ms
      message: 'load-balancer-api-external: resolved host name a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:43:17Z"
    - latency: 4.613407ms
      message: 'load-balancer-api-external: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:42:17Z"
    - latency: 6.362145ms
      message: 'load-balancer-api-external: resolved host name a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:42:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T19:04:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-11-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-11.ec2.internal
      uid: 9f638746-4fe3-4c07-b54b-55cb927f0019
    resourceVersion: "61881"
    uid: 97d9487c-14c8-4c49-87be-c7432b9dabb3
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kzdhn
    targetEndpoint: a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:10:17Z"
      message: 'load-balancer-api-internal: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.820948ms
      message: 'load-balancer-api-internal: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:46:17Z"
    - latency: 6.767471ms
      message: 'load-balancer-api-internal: resolved host name a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:46:17Z"
    - latency: 4.01222ms
      message: 'load-balancer-api-internal: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:45:17Z"
    - latency: 6.546478ms
      message: 'load-balancer-api-internal: resolved host name a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:45:17Z"
    - latency: 4.095412ms
      message: 'load-balancer-api-internal: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:44:17Z"
    - latency: 7.53601ms
      message: 'load-balancer-api-internal: resolved host name a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:44:17Z"
    - latency: 3.845484ms
      message: 'load-balancer-api-internal: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:43:17Z"
    - latency: 6.65342ms
      message: 'load-balancer-api-internal: resolved host name a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:43:17Z"
    - latency: 4.607197ms
      message: 'load-balancer-api-internal: tcp connection to a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:42:17Z"
    - latency: 6.380263ms
      message: 'load-balancer-api-internal: resolved host name a33529ea16fd8408b95c886fa37e9116-cd2d913fde1ac155.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:42:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T19:04:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-11-to-network-check-target-ip-10-0-128-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-11.ec2.internal
      uid: 9f638746-4fe3-4c07-b54b-55cb927f0019
    resourceVersion: "61876"
    uid: e6630b24-d049-426a-8bb5-0407b2c8949c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kzdhn
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:11:17Z"
      message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.91447ms
      message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:46:17Z"
    - latency: 1.835117ms
      message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:45:17Z"
    - latency: 2.166717ms
      message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:44:17Z"
    - latency: 2.090694ms
      message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:43:17Z"
    - latency: 2.002443ms
      message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:42:17Z"
    - latency: 2.042411ms
      message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:41:17Z"
    - latency: 1.904945ms
      message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:40:17Z"
    - latency: 1.550225ms
      message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:39:17Z"
    - latency: 1.795311ms
      message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:38:17Z"
    - latency: 1.755705ms
      message: 'network-check-target-ip-10-0-128-42: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:37:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T19:04:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-11-to-network-check-target-ip-10-0-135-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-11.ec2.internal
      uid: 9f638746-4fe3-4c07-b54b-55cb927f0019
    resourceVersion: "61875"
    uid: a526caa2-282c-4e07-9520-e7755998d995
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kzdhn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:11:17Z"
      message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.024188ms
      message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:46:17Z"
    - latency: 862.238µs
      message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:45:17Z"
    - latency: 1.547786ms
      message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:44:17Z"
    - latency: 1.029496ms
      message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:43:17Z"
    - latency: 870.023µs
      message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:42:17Z"
    - latency: 1.368661ms
      message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:41:17Z"
    - latency: 1.096057ms
      message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:40:17Z"
    - latency: 1.064507ms
      message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:39:17Z"
    - latency: 1.075188ms
      message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:38:17Z"
    - latency: 872.166µs
      message: 'network-check-target-ip-10-0-135-11: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:37:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T19:04:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-11-to-network-check-target-ip-10-0-139-123
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-11.ec2.internal
      uid: 9f638746-4fe3-4c07-b54b-55cb927f0019
    resourceVersion: "61877"
    uid: 3c6edf31-9304-48f5-aa27-5a3c73719ed7
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kzdhn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:11:17Z"
      message: 'network-check-target-ip-10-0-139-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.246616ms
      message: 'network-check-target-ip-10-0-139-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:46:17Z"
    - latency: 2.373433ms
      message: 'network-check-target-ip-10-0-139-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:45:17Z"
    - latency: 1.886944ms
      message: 'network-check-target-ip-10-0-139-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:44:17Z"
    - latency: 2.216229ms
      message: 'network-check-target-ip-10-0-139-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:43:17Z"
    - latency: 2.114756ms
      message: 'network-check-target-ip-10-0-139-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:42:17Z"
    - latency: 2.557363ms
      message: 'network-check-target-ip-10-0-139-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:41:17Z"
    - latency: 2.482155ms
      message: 'network-check-target-ip-10-0-139-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:40:17Z"
    - latency: 2.039005ms
      message: 'network-check-target-ip-10-0-139-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:39:17Z"
    - latency: 2.078011ms
      message: 'network-check-target-ip-10-0-139-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:38:17Z"
    - latency: 2.001294ms
      message: 'network-check-target-ip-10-0-139-123: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:37:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T19:04:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-11-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-11.ec2.internal
      uid: 9f638746-4fe3-4c07-b54b-55cb927f0019
    resourceVersion: "61878"
    uid: c0c7799f-4d39-4802-881c-5b16406bc5fb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-kzdhn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T19:10:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.96µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:46:17Z"
    - latency: 1.707357ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:46:17Z"
    - latency: 1.27252ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:45:17Z"
    - latency: 1.697063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:45:17Z"
    - latency: 1.00323ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:44:17Z"
    - latency: 1.782442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:44:17Z"
    - latency: 1.167844ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:43:17Z"
    - latency: 1.854567ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:43:17Z"
    - latency: 873.202µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T19:42:17Z"
    - latency: 1.877445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T19:42:17Z"
kind: List
metadata:
  resourceVersion: ""