apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:57:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-132-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-132.ec2.internal
      uid: b63bacd3-eafb-44be-a9b0-d69e6c2bdcf4
    resourceVersion: "35427"
    uid: 3147ad9d-6e6d-4802-985e-9b80f7a20380
  spec:
    sourcePod: network-check-source-6f78d59f99-zq8h7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:04:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.372305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:00:46Z"
    - latency: 891.328µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:59:46Z"
    - latency: 896.998µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:58:46Z"
    - latency: 1.175175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:57:46Z"
    - latency: 1.017471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:56:46Z"
    - latency: 873.216µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:55:46Z"
    - latency: 1.029944ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:54:46Z"
    - latency: 898.126µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:53:46Z"
    - latency: 1.152857ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:52:46Z"
    - latency: 1.176006ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:51:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:57:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-132-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-132.ec2.internal
      uid: b63bacd3-eafb-44be-a9b0-d69e6c2bdcf4
    resourceVersion: "38638"
    uid: 87f732cd-4418-4265-b4c6-4916f4fa4c8e
  spec:
    sourcePod: network-check-source-6f78d59f99-zq8h7
    targetEndpoint: ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:03:47Z"
      message: 'load-balancer-api-external: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 13.60197ms
      message: 'load-balancer-api-external: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:03:46Z"
    - latency: 8.828392ms
      message: 'load-balancer-api-external: resolved host name ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:03:46Z"
    - latency: 16.619729ms
      message: 'load-balancer-api-external: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:02:46Z"
    - latency: 9.98508ms
      message: 'load-balancer-api-external: resolved host name ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:02:46Z"
    - latency: 17.861734ms
      message: 'load-balancer-api-external: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:01:46Z"
    - latency: 8.861866ms
      message: 'load-balancer-api-external: resolved host name ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:01:46Z"
    - latency: 17.297744ms
      message: 'load-balancer-api-external: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:00:46Z"
    - latency: 7.50729ms
      message: 'load-balancer-api-external: resolved host name ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:00:46Z"
    - latency: 19.128365ms
      message: 'load-balancer-api-external: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:59:46Z"
    - latency: 8.696279ms
      message: 'load-balancer-api-external: resolved host name ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:59:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:57:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-132-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-132.ec2.internal
      uid: b63bacd3-eafb-44be-a9b0-d69e6c2bdcf4
    resourceVersion: "38639"
    uid: acd30eb2-e62c-465e-9584-2b60df81ca6f
  spec:
    sourcePod: network-check-source-6f78d59f99-zq8h7
    targetEndpoint: ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:03:47Z"
      message: 'load-balancer-api-internal: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 18.433333ms
      message: 'load-balancer-api-internal: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:03:46Z"
    - latency: 8.795894ms
      message: 'load-balancer-api-internal: resolved host name ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:03:46Z"
    - latency: 14.624985ms
      message: 'load-balancer-api-internal: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:02:46Z"
    - latency: 9.929118ms
      message: 'load-balancer-api-internal: resolved host name ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:02:46Z"
    - latency: 17.467676ms
      message: 'load-balancer-api-internal: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:01:46Z"
    - latency: 8.770214ms
      message: 'load-balancer-api-internal: resolved host name ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:01:46Z"
    - latency: 17.277579ms
      message: 'load-balancer-api-internal: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:00:46Z"
    - latency: 7.456699ms
      message: 'load-balancer-api-internal: resolved host name ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:00:46Z"
    - latency: 18.237282ms
      message: 'load-balancer-api-internal: tcp connection to ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:59:46Z"
    - latency: 8.729939ms
      message: 'load-balancer-api-internal: resolved host name ad88ca1e08e9f487384680196d8d0ff1-a0b18f307c31c829.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:59:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:57:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-132-to-network-check-target-ip-10-0-138-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-132.ec2.internal
      uid: b63bacd3-eafb-44be-a9b0-d69e6c2bdcf4
    resourceVersion: "35426"
    uid: 773d57ec-10ce-47b2-a115-5b9a75938a51
  spec:
    sourcePod: network-check-source-6f78d59f99-zq8h7
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:04:46Z"
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.287702ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:00:46Z"
    - latency: 2.01125ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:59:46Z"
    - latency: 2.061444ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:58:46Z"
    - latency: 2.152179ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:57:46Z"
    - latency: 2.257556ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:56:46Z"
    - latency: 1.860336ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:55:46Z"
    - latency: 2.207339ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:54:46Z"
    - latency: 2.063788ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:53:46Z"
    - latency: 1.905022ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:52:46Z"
    - latency: 2.219236ms
      message: 'network-check-target-ip-10-0-138-200: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:51:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:57:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-132-to-network-check-target-ip-10-0-139-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-132.ec2.internal
      uid: b63bacd3-eafb-44be-a9b0-d69e6c2bdcf4
    resourceVersion: "35425"
    uid: a70f963a-3d5d-450d-904c-137835309b32
  spec:
    sourcePod: network-check-source-6f78d59f99-zq8h7
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:04:46Z"
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.107752ms
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:00:46Z"
    - latency: 1.67351ms
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:59:46Z"
    - latency: 1.735445ms
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:58:46Z"
    - latency: 1.839563ms
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:57:46Z"
    - latency: 1.689266ms
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:56:46Z"
    - latency: 1.825348ms
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:55:46Z"
    - latency: 1.892908ms
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:54:46Z"
    - latency: 1.986329ms
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:53:46Z"
    - latency: 1.785959ms
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:52:46Z"
    - latency: 1.830515ms
      message: 'network-check-target-ip-10-0-139-80: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:51:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:57:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-132-to-network-check-target-ip-10-0-140-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-132.ec2.internal
      uid: b63bacd3-eafb-44be-a9b0-d69e6c2bdcf4
    resourceVersion: "35424"
    uid: 85b41aad-397e-40b8-83b1-ffe6378017a5
  spec:
    sourcePod: network-check-source-6f78d59f99-zq8h7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:04:46Z"
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.353284ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:00:46Z"
    - latency: 978.735µs
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:59:46Z"
    - latency: 788.183µs
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:58:46Z"
    - latency: 944.63µs
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:57:46Z"
    - latency: 907.041µs
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:56:46Z"
    - latency: 840.48µs
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:55:46Z"
    - latency: 809.132µs
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:54:46Z"
    - latency: 1.065616ms
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:53:46Z"
    - latency: 797.154µs
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:52:46Z"
    - latency: 866.62µs
      message: 'network-check-target-ip-10-0-140-132: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:51:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T02:57:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-132-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-132.ec2.internal
      uid: b63bacd3-eafb-44be-a9b0-d69e6c2bdcf4
    resourceVersion: "38637"
    uid: e0aa5e64-498b-4bf4-9ce6-049d2e4d0b95
  spec:
    sourcePod: network-check-source-6f78d59f99-zq8h7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:03:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 752.221µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:03:46Z"
    - latency: 1.831705ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:03:46Z"
    - latency: 926.608µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:02:46Z"
    - latency: 1.950403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:02:46Z"
    - latency: 822.126µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:01:46Z"
    - latency: 1.652713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:01:46Z"
    - latency: 1.012308ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T04:00:46Z"
    - latency: 2.087276ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T04:00:46Z"
    - latency: 974.475µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:59:46Z"
    - latency: 1.867852ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:59:46Z"
kind: List
metadata:
  resourceVersion: ""