apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:57:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-32-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-32.us-west-1.compute.internal
      uid: 41049a52-6004-4e5b-9177-522bf4004624
    resourceVersion: "100597"
    uid: 2cd33a8f-c4f1-4080-893e-ef2d81107f76
  spec:
    sourcePod: network-check-source-6f78d59f99-rdsd9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:04:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.372212ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:32Z"
    - latency: 1.97037ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:32Z"
    - latency: 1.348037ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:32Z"
    - latency: 1.006283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:32Z"
    - latency: 898.324µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:32Z"
    - latency: 1.90091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:32Z"
    - latency: 801.456µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:32Z"
    - latency: 1.404197ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:32Z"
    - latency: 1.111202ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:32Z"
    - latency: 1.435601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:57:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-32-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-32.us-west-1.compute.internal
      uid: 41049a52-6004-4e5b-9177-522bf4004624
    resourceVersion: "103276"
    uid: eff4110e-99c5-4169-ade2-da174b049cf3
  spec:
    sourcePod: network-check-source-6f78d59f99-rdsd9
    targetEndpoint: a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:03:32Z"
      message: 'load-balancer-api-external: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.912978ms
      message: 'load-balancer-api-external: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:03:32Z"
    - latency: 9.287932ms
      message: 'load-balancer-api-external: resolved host name a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:03:32Z"
    - latency: 52.609167ms
      message: 'load-balancer-api-external: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:02:32Z"
    - latency: 6.26062ms
      message: 'load-balancer-api-external: resolved host name a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:02:32Z"
    - latency: 53.709009ms
      message: 'load-balancer-api-external: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:01:32Z"
    - latency: 8.785164ms
      message: 'load-balancer-api-external: resolved host name a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:01:32Z"
    - latency: 54.189918ms
      message: 'load-balancer-api-external: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:32Z"
    - latency: 6.765491ms
      message: 'load-balancer-api-external: resolved host name a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:00:32Z"
    - latency: 52.027605ms
      message: 'load-balancer-api-external: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:32Z"
    - latency: 7.103905ms
      message: 'load-balancer-api-external: resolved host name a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:59:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:57:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-32-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-32.us-west-1.compute.internal
      uid: 41049a52-6004-4e5b-9177-522bf4004624
    resourceVersion: "103277"
    uid: b360a20a-554f-4333-b4a9-e12e44531d43
  spec:
    sourcePod: network-check-source-6f78d59f99-rdsd9
    targetEndpoint: a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:03:32Z"
      message: 'load-balancer-api-internal: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.036829ms
      message: 'load-balancer-api-internal: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:03:32Z"
    - latency: 9.251035ms
      message: 'load-balancer-api-internal: resolved host name a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:03:32Z"
    - latency: 52.573802ms
      message: 'load-balancer-api-internal: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:02:32Z"
    - latency: 6.313431ms
      message: 'load-balancer-api-internal: resolved host name a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:02:32Z"
    - latency: 53.57067ms
      message: 'load-balancer-api-internal: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:01:32Z"
    - latency: 8.755082ms
      message: 'load-balancer-api-internal: resolved host name a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:01:32Z"
    - latency: 52.924685ms
      message: 'load-balancer-api-internal: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:32Z"
    - latency: 6.707067ms
      message: 'load-balancer-api-internal: resolved host name a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:00:32Z"
    - latency: 58.386057ms
      message: 'load-balancer-api-internal: tcp connection to a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:32Z"
    - latency: 7.043349ms
      message: 'load-balancer-api-internal: resolved host name a2a55f6a5a807453fa6f77ca235301fa-4f791996f38f588f.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:59:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:57:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-32-to-network-check-target-ip-10-0-137-32
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-32.us-west-1.compute.internal
      uid: 41049a52-6004-4e5b-9177-522bf4004624
    resourceVersion: "100593"
    uid: 2791a282-496f-4161-94b9-ba25589b134f
  spec:
    sourcePod: network-check-source-6f78d59f99-rdsd9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:04:32Z"
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.845849ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:32Z"
    - latency: 2.071882ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:32Z"
    - latency: 1.289433ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:32Z"
    - latency: 1.00552ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:32Z"
    - latency: 908.148µs
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:32Z"
    - latency: 1.420059ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:32Z"
    - latency: 893.928µs
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:32Z"
    - latency: 2.287874ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:32Z"
    - latency: 929.273µs
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:32Z"
    - latency: 1.328105ms
      message: 'network-check-target-ip-10-0-137-32: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:57:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-32-to-network-check-target-ip-10-0-138-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-32.us-west-1.compute.internal
      uid: 41049a52-6004-4e5b-9177-522bf4004624
    resourceVersion: "100594"
    uid: 017d34d9-ff93-4ae3-95e3-f332454086a3
  spec:
    sourcePod: network-check-source-6f78d59f99-rdsd9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:04:32Z"
      message: 'network-check-target-ip-10-0-138-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.602875ms
      message: 'network-check-target-ip-10-0-138-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:32Z"
    - latency: 2.657196ms
      message: 'network-check-target-ip-10-0-138-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:32Z"
    - latency: 1.682233ms
      message: 'network-check-target-ip-10-0-138-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:32Z"
    - latency: 2.576089ms
      message: 'network-check-target-ip-10-0-138-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:32Z"
    - latency: 2.171688ms
      message: 'network-check-target-ip-10-0-138-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:32Z"
    - latency: 2.157169ms
      message: 'network-check-target-ip-10-0-138-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:32Z"
    - latency: 1.894192ms
      message: 'network-check-target-ip-10-0-138-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:32Z"
    - latency: 3.152319ms
      message: 'network-check-target-ip-10-0-138-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:32Z"
    - latency: 2.003288ms
      message: 'network-check-target-ip-10-0-138-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:32Z"
    - latency: 2.154414ms
      message: 'network-check-target-ip-10-0-138-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:57:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-32-to-network-check-target-ip-10-0-142-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-32.us-west-1.compute.internal
      uid: 41049a52-6004-4e5b-9177-522bf4004624
    resourceVersion: "100596"
    uid: 15f55d90-14cf-4af2-ace7-e10b78aafa64
  spec:
    sourcePod: network-check-source-6f78d59f99-rdsd9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:04:32Z"
      message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 10.328751ms
      message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:32Z"
    - latency: 14.705758ms
      message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:32Z"
    - latency: 1.622535ms
      message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:32Z"
    - latency: 2.148324ms
      message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:32Z"
    - latency: 2.612326ms
      message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:32Z"
    - latency: 3.135254ms
      message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:32Z"
    - latency: 2.047516ms
      message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:32Z"
    - latency: 3.763334ms
      message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:32Z"
    - latency: 2.410934ms
      message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:32Z"
    - latency: 2.245683ms
      message: 'network-check-target-ip-10-0-142-210: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:57:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-32-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-32.us-west-1.compute.internal
      uid: 41049a52-6004-4e5b-9177-522bf4004624
    resourceVersion: "103275"
    uid: 14bfad28-0264-4b60-b007-36067d7556e9
  spec:
    sourcePod: network-check-source-6f78d59f99-rdsd9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:03:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 918.969µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:03:32Z"
    - latency: 2.022416ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:03:32Z"
    - latency: 898.732µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:02:32Z"
    - latency: 1.994184ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:02:32Z"
    - latency: 903.227µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:01:32Z"
    - latency: 1.91824ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:01:32Z"
    - latency: 8.230639ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:00:32Z"
    - latency: 2.252626ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:00:32Z"
    - latency: 934.868µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:59:32Z"
    - latency: 2.573704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:59:32Z"
kind: List
metadata:
  resourceVersion: ""