apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-147-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-147.ec2.internal
      uid: ec06eb65-9f88-483e-abd0-898a27236a42
    resourceVersion: "53041"
    uid: 9816351a-c595-438f-8e26-24b1a9f98388
  spec:
    sourcePod: network-check-source-6f8b768455-q8779
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:46:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.289256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:56Z"
    - latency: 1.25524ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:56Z"
    - latency: 1.149482ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:56Z"
    - latency: 1.074968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:56Z"
    - latency: 730.34µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:56Z"
    - latency: 1.20091ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:56Z"
    - latency: 1.189889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:56Z"
    - latency: 1.263916ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:56Z"
    - latency: 1.457022ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:56Z"
    - latency: 1.302183ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-147-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-147.ec2.internal
      uid: ec06eb65-9f88-483e-abd0-898a27236a42
    resourceVersion: "54589"
    uid: c7af2f3e-ebb7-41a7-a9a8-ce9d6a8255c9
  spec:
    sourcePod: network-check-source-6f8b768455-q8779
    targetEndpoint: a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:45:56Z"
      message: 'load-balancer-api-external: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.27525ms
      message: 'load-balancer-api-external: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:09:56Z"
    - latency: 7.675764ms
      message: 'load-balancer-api-external: resolved host name a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:09:56Z"
    - latency: 4.074853ms
      message: 'load-balancer-api-external: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:56Z"
    - latency: 6.39279ms
      message: 'load-balancer-api-external: resolved host name a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:08:56Z"
    - latency: 4.306212ms
      message: 'load-balancer-api-external: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:56Z"
    - latency: 7.21652ms
      message: 'load-balancer-api-external: resolved host name a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:56Z"
    - latency: 4.458393ms
      message: 'load-balancer-api-external: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:56Z"
    - latency: 6.805066ms
      message: 'load-balancer-api-external: resolved host name a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:56Z"
    - latency: 4.019604ms
      message: 'load-balancer-api-external: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:56Z"
    - latency: 7.60088ms
      message: 'load-balancer-api-external: resolved host name a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:05:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-147-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-147.ec2.internal
      uid: ec06eb65-9f88-483e-abd0-898a27236a42
    resourceVersion: "54588"
    uid: d2ae5063-6ea4-4c47-b773-52617ba6c011
  spec:
    sourcePod: network-check-source-6f8b768455-q8779
    targetEndpoint: a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:45:56Z"
      message: 'load-balancer-api-internal: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.341874ms
      message: 'load-balancer-api-internal: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:09:56Z"
    - latency: 7.603701ms
      message: 'load-balancer-api-internal: resolved host name a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:09:56Z"
    - latency: 3.952654ms
      message: 'load-balancer-api-internal: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:56Z"
    - latency: 6.276355ms
      message: 'load-balancer-api-internal: resolved host name a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:08:56Z"
    - latency: 4.264315ms
      message: 'load-balancer-api-internal: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:56Z"
    - latency: 7.189814ms
      message: 'load-balancer-api-internal: resolved host name a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:56Z"
    - latency: 4.395796ms
      message: 'load-balancer-api-internal: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:56Z"
    - latency: 6.70376ms
      message: 'load-balancer-api-internal: resolved host name a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:56Z"
    - latency: 5.000903ms
      message: 'load-balancer-api-internal: tcp connection to a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:56Z"
    - latency: 7.465244ms
      message: 'load-balancer-api-internal: resolved host name a2079c2c13e6e4b1cbf590c2b52102e6-4cb7355be5966266.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:05:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-147-to-network-check-target-ip-10-0-134-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-147.ec2.internal
      uid: ec06eb65-9f88-483e-abd0-898a27236a42
    resourceVersion: "53039"
    uid: 9b8ecd99-0927-4701-9e0e-109143a16ab6
  spec:
    sourcePod: network-check-source-6f8b768455-q8779
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:46:56Z"
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.130066ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:56Z"
    - latency: 2.147387ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:56Z"
    - latency: 2.185977ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:56Z"
    - latency: 2.132811ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:56Z"
    - latency: 1.570038ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:56Z"
    - latency: 1.979445ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:56Z"
    - latency: 2.145019ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:56Z"
    - latency: 2.132636ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:56Z"
    - latency: 1.958153ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:56Z"
    - latency: 1.949601ms
      message: 'network-check-target-ip-10-0-134-115: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-147-to-network-check-target-ip-10-0-139-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-147.ec2.internal
      uid: ec06eb65-9f88-483e-abd0-898a27236a42
    resourceVersion: "53040"
    uid: 24270023-8aed-437a-988f-72062515c13f
  spec:
    sourcePod: network-check-source-6f8b768455-q8779
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:46:56Z"
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.133285ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:56Z"
    - latency: 2.478364ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:56Z"
    - latency: 2.329307ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:56Z"
    - latency: 2.529607ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:56Z"
    - latency: 2.457087ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:56Z"
    - latency: 2.064692ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:56Z"
    - latency: 2.281872ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:56Z"
    - latency: 2.134675ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:56Z"
    - latency: 2.223596ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:56Z"
    - latency: 2.410413ms
      message: 'network-check-target-ip-10-0-139-142: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-147-to-network-check-target-ip-10-0-139-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-147.ec2.internal
      uid: ec06eb65-9f88-483e-abd0-898a27236a42
    resourceVersion: "53038"
    uid: e9fe6ede-c7c1-4ea5-961c-dcb03d64b17f
  spec:
    sourcePod: network-check-source-6f8b768455-q8779
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:46:56Z"
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.967µs
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:56Z"
    - latency: 848.922µs
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:56Z"
    - latency: 942.974µs
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:56Z"
    - latency: 1.608778ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:04:56Z"
    - latency: 1.6043ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:03:56Z"
    - latency: 1.029329ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:02:56Z"
    - latency: 955.409µs
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:01:56Z"
    - latency: 847.348µs
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:00:56Z"
    - latency: 1.10951ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:59:56Z"
    - latency: 1.307358ms
      message: 'network-check-target-ip-10-0-139-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T23:58:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T23:39:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-147-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-147.ec2.internal
      uid: ec06eb65-9f88-483e-abd0-898a27236a42
    resourceVersion: "54587"
    uid: ba9e833c-5503-4df9-99b8-9ef03d7853d8
  spec:
    sourcePod: network-check-source-6f8b768455-q8779
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T23:45:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.451µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:09:56Z"
    - latency: 2.00538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:09:56Z"
    - latency: 866.039µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:08:56Z"
    - latency: 1.895741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:08:56Z"
    - latency: 978.569µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:07:56Z"
    - latency: 1.756256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:07:56Z"
    - latency: 1.103217ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:06:56Z"
    - latency: 1.88157ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:06:56Z"
    - latency: 1.018803ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T00:05:56Z"
    - latency: 1.831112ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T00:05:56Z"
kind: List
metadata:
  resourceVersion: ""