apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: a9f07317-2f07-4f6e-bd7f-2bf3dd5c8a73
    resourceVersion: "62887"
    uid: 0ede86da-6dc1-44ac-b233-7c6c52596109
  spec:
    sourcePod: network-check-source-7bc5b6bf85-z4cnj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:33:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.879µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:08:38Z"
    - latency: 912.571µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:07:38Z"
    - latency: 1.482106ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:06:38Z"
    - latency: 1.051129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:05:38Z"
    - latency: 1.435222ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:04:38Z"
    - latency: 998.784µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:03:38Z"
    - latency: 1.193046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:02:38Z"
    - latency: 1.326592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:01:38Z"
    - latency: 1.566147ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:00:38Z"
    - latency: 1.54288ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:59:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: a9f07317-2f07-4f6e-bd7f-2bf3dd5c8a73
    resourceVersion: "62889"
    uid: bc543ba7-4ce1-4407-b5b4-fce4c6ba7380
  spec:
    sourcePod: network-check-source-7bc5b6bf85-z4cnj
    targetEndpoint: aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:32:38Z"
      message: 'load-balancer-api-external: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.080076ms
      message: 'load-balancer-api-external: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:08:38Z"
    - latency: 9.212901ms
      message: 'load-balancer-api-external: resolved host name aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:08:38Z"
    - latency: 4.798125ms
      message: 'load-balancer-api-external: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:07:38Z"
    - latency: 9.779085ms
      message: 'load-balancer-api-external: resolved host name aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:07:38Z"
    - latency: 4.13333ms
      message: 'load-balancer-api-external: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:06:38Z"
    - latency: 9.45337ms
      message: 'load-balancer-api-external: resolved host name aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:06:38Z"
    - latency: 4.806512ms
      message: 'load-balancer-api-external: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:05:38Z"
    - latency: 8.282465ms
      message: 'load-balancer-api-external: resolved host name aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:05:38Z"
    - latency: 5.023483ms
      message: 'load-balancer-api-external: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:04:38Z"
    - latency: 7.77667ms
      message: 'load-balancer-api-external: resolved host name aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:04:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: a9f07317-2f07-4f6e-bd7f-2bf3dd5c8a73
    resourceVersion: "62888"
    uid: ee4760fe-76a8-4566-be5e-a5e89672c825
  spec:
    sourcePod: network-check-source-7bc5b6bf85-z4cnj
    targetEndpoint: aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:32:38Z"
      message: 'load-balancer-api-internal: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.086239ms
      message: 'load-balancer-api-internal: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:08:38Z"
    - latency: 9.300879ms
      message: 'load-balancer-api-internal: resolved host name aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:08:38Z"
    - latency: 11.614856ms
      message: 'load-balancer-api-internal: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:07:38Z"
    - latency: 9.744929ms
      message: 'load-balancer-api-internal: resolved host name aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:07:38Z"
    - latency: 4.078086ms
      message: 'load-balancer-api-internal: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:06:38Z"
    - latency: 9.376398ms
      message: 'load-balancer-api-internal: resolved host name aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:06:38Z"
    - latency: 4.177978ms
      message: 'load-balancer-api-internal: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:05:38Z"
    - latency: 8.256841ms
      message: 'load-balancer-api-internal: resolved host name aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:05:38Z"
    - latency: 5.039304ms
      message: 'load-balancer-api-internal: tcp connection to aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:04:38Z"
    - latency: 7.865898ms
      message: 'load-balancer-api-internal: resolved host name aa9931d5f4fb542ca9ad6fb977f18caa-0099c73e952f5f1b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:04:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-network-check-target-ip-10-0-128-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: a9f07317-2f07-4f6e-bd7f-2bf3dd5c8a73
    resourceVersion: "62885"
    uid: 4d630cc0-b895-4db6-8f74-e580b2cba3d5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-z4cnj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:33:38Z"
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.480185ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:08:38Z"
    - latency: 2.37914ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:07:38Z"
    - latency: 2.283506ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:06:38Z"
    - latency: 2.19473ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:05:38Z"
    - latency: 2.573386ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:04:38Z"
    - latency: 2.729162ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:03:38Z"
    - latency: 2.478859ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:02:38Z"
    - latency: 2.80661ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:01:38Z"
    - latency: 2.902153ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:00:38Z"
    - latency: 2.370562ms
      message: 'network-check-target-ip-10-0-128-147: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:59:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-network-check-target-ip-10-0-131-213
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: a9f07317-2f07-4f6e-bd7f-2bf3dd5c8a73
    resourceVersion: "62884"
    uid: eba8e374-b9c8-4642-bbc7-d7696691f44a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-z4cnj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:33:38Z"
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.431168ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:08:38Z"
    - latency: 2.686794ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:07:38Z"
    - latency: 2.354295ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:06:38Z"
    - latency: 2.513703ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:05:38Z"
    - latency: 2.623209ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:04:38Z"
    - latency: 2.40894ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:03:38Z"
    - latency: 2.339287ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:02:38Z"
    - latency: 2.77319ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:01:38Z"
    - latency: 2.63438ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:00:38Z"
    - latency: 2.86658ms
      message: 'network-check-target-ip-10-0-131-213: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:59:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-network-check-target-ip-10-0-132-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: a9f07317-2f07-4f6e-bd7f-2bf3dd5c8a73
    resourceVersion: "62883"
    uid: f96759eb-7f92-45ee-972d-f3ba1b590ddf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-z4cnj
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:33:38Z"
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.234557ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:08:38Z"
    - latency: 1.113032ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:07:38Z"
    - latency: 974.737µs
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:06:38Z"
    - latency: 1.909326ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:05:38Z"
    - latency: 1.588415ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:04:38Z"
    - latency: 1.014029ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:03:38Z"
    - latency: 857.236µs
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:02:38Z"
    - latency: 1.410837ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:01:38Z"
    - latency: 1.507275ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:00:38Z"
    - latency: 1.126534ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T01:59:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T01:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-244-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-244.ec2.internal
      uid: a9f07317-2f07-4f6e-bd7f-2bf3dd5c8a73
    resourceVersion: "62886"
    uid: 8e95f4f4-1dc6-4685-b745-c30aa5ce003b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-z4cnj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T01:32:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 823.862µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:08:38Z"
    - latency: 2.146926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:08:38Z"
    - latency: 750.5µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:07:38Z"
    - latency: 2.07289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:07:38Z"
    - latency: 899.388µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:06:38Z"
    - latency: 1.962676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:06:38Z"
    - latency: 1.24712ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:05:38Z"
    - latency: 2.026562ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:05:38Z"
    - latency: 909.125µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T02:04:38Z"
    - latency: 1.978511ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T02:04:38Z"
kind: List
metadata:
  resourceVersion: ""