apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:38:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-57-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-57.ec2.internal
      uid: 698b64d0-58b3-46ea-b27e-0bafb57e158b
    resourceVersion: "103074"
    uid: 6a1b08e3-5b4a-499a-a7bb-33f59c73cfc8
  spec:
    sourcePod: network-check-source-989f8b8dc-ktssk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:45:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 974.84µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:23:27Z"
    - latency: 1.247318ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:22:27Z"
    - latency: 990.934µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:21:27Z"
    - latency: 1.094082ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:20:27Z"
    - latency: 1.007224ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:19:27Z"
    - latency: 1.312876ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:18:27Z"
    - latency: 1.025683ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:17:27Z"
    - latency: 1.084014ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:16:27Z"
    - latency: 969.91µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:15:27Z"
    - latency: 1.167678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:38:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-57-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-57.ec2.internal
      uid: 698b64d0-58b3-46ea-b27e-0bafb57e158b
    resourceVersion: "101210"
    uid: 8c7db08c-4757-40f5-ab75-5d472b4b9904
  spec:
    sourcePod: network-check-source-989f8b8dc-ktssk
    targetEndpoint: a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:44:27Z"
      message: 'load-balancer-api-external: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.380222ms
      message: 'load-balancer-api-external: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:20:27Z"
    - latency: 5.388437ms
      message: 'load-balancer-api-external: resolved host name a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:20:27Z"
    - latency: 5.814463ms
      message: 'load-balancer-api-external: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:19:27Z"
    - latency: 5.609551ms
      message: 'load-balancer-api-external: resolved host name a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:19:27Z"
    - latency: 5.433058ms
      message: 'load-balancer-api-external: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:18:27Z"
    - latency: 6.595175ms
      message: 'load-balancer-api-external: resolved host name a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:18:27Z"
    - latency: 5.559092ms
      message: 'load-balancer-api-external: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:17:27Z"
    - latency: 5.097223ms
      message: 'load-balancer-api-external: resolved host name a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:17:27Z"
    - latency: 5.796052ms
      message: 'load-balancer-api-external: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:16:27Z"
    - latency: 5.335623ms
      message: 'load-balancer-api-external: resolved host name a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:16:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:38:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-57-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-57.ec2.internal
      uid: 698b64d0-58b3-46ea-b27e-0bafb57e158b
    resourceVersion: "101211"
    uid: cd534210-b4e1-4e11-ad15-6aa9d2ad82b6
  spec:
    sourcePod: network-check-source-989f8b8dc-ktssk
    targetEndpoint: a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:44:27Z"
      message: 'load-balancer-api-internal: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.071378ms
      message: 'load-balancer-api-internal: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:20:27Z"
    - latency: 3.565555ms
      message: 'load-balancer-api-internal: resolved host name a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:20:27Z"
    - latency: 4.035176ms
      message: 'load-balancer-api-internal: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:19:27Z"
    - latency: 2.027034ms
      message: 'load-balancer-api-internal: resolved host name a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:19:27Z"
    - latency: 5.289821ms
      message: 'load-balancer-api-internal: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:18:27Z"
    - latency: 2.116102ms
      message: 'load-balancer-api-internal: resolved host name a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:18:27Z"
    - latency: 4.061946ms
      message: 'load-balancer-api-internal: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:17:27Z"
    - latency: 3.330675ms
      message: 'load-balancer-api-internal: resolved host name a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:17:27Z"
    - latency: 5.57414ms
      message: 'load-balancer-api-internal: tcp connection to a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:16:27Z"
    - latency: 2.397317ms
      message: 'load-balancer-api-internal: resolved host name a9e5214c7506644cb80ef560edbc437e-108a202261685530.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:16:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:38:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-57-to-network-check-target-ip-10-0-131-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-57.ec2.internal
      uid: 698b64d0-58b3-46ea-b27e-0bafb57e158b
    resourceVersion: "103071"
    uid: 5667a62f-727b-4fe9-92cf-16e5efd23bbe
  spec:
    sourcePod: network-check-source-989f8b8dc-ktssk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:45:27Z"
      message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.327845ms
      message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:23:27Z"
    - latency: 2.413417ms
      message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:22:27Z"
    - latency: 2.078575ms
      message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:21:27Z"
    - latency: 2.535262ms
      message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:20:27Z"
    - latency: 2.39277ms
      message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:19:27Z"
    - latency: 2.559295ms
      message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:18:27Z"
    - latency: 2.55275ms
      message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:17:27Z"
    - latency: 2.036705ms
      message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:16:27Z"
    - latency: 1.852007ms
      message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:15:27Z"
    - latency: 2.513903ms
      message: 'network-check-target-ip-10-0-131-45: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:38:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-57-to-network-check-target-ip-10-0-131-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-57.ec2.internal
      uid: 698b64d0-58b3-46ea-b27e-0bafb57e158b
    resourceVersion: "103072"
    uid: 18217c35-6b93-4eb9-ab4a-f0f109a6eb6e
  spec:
    sourcePod: network-check-source-989f8b8dc-ktssk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:45:27Z"
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.014694ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:23:27Z"
    - latency: 1.158518ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:22:27Z"
    - latency: 1.267294ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:21:27Z"
    - latency: 1.074227ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:20:27Z"
    - latency: 1.354957ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:19:27Z"
    - latency: 1.322859ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:18:27Z"
    - latency: 1.100716ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:17:27Z"
    - latency: 1.330474ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:16:27Z"
    - latency: 1.286883ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:15:27Z"
    - latency: 846.943µs
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:38:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-57-to-network-check-target-ip-10-0-142-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-57.ec2.internal
      uid: 698b64d0-58b3-46ea-b27e-0bafb57e158b
    resourceVersion: "103073"
    uid: 3c2adf79-7ac3-4d08-8165-8bbdf0364ca0
  spec:
    sourcePod: network-check-source-989f8b8dc-ktssk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:45:27Z"
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.642828ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:23:27Z"
    - latency: 2.511364ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:22:27Z"
    - latency: 2.684793ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:21:27Z"
    - latency: 2.471612ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:20:27Z"
    - latency: 2.502792ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:19:27Z"
    - latency: 2.523105ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:18:27Z"
    - latency: 2.545127ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:17:27Z"
    - latency: 2.525028ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:16:27Z"
    - latency: 2.3871ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:15:27Z"
    - latency: 2.525657ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:38:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-57-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-57.ec2.internal
      uid: 698b64d0-58b3-46ea-b27e-0bafb57e158b
    resourceVersion: "101209"
    uid: 186e6867-96d8-4e6e-96c1-5d68c71c11d1
  spec:
    sourcePod: network-check-source-989f8b8dc-ktssk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:44:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 934.596µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:20:27Z"
    - latency: 1.615967ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:20:27Z"
    - latency: 1.244804ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:19:27Z"
    - latency: 1.868859ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:19:27Z"
    - latency: 964.701µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:18:27Z"
    - latency: 1.953052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:18:27Z"
    - latency: 981.995µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:17:27Z"
    - latency: 2.525631ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:17:27Z"
    - latency: 1.198659ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:16:27Z"
    - latency: 1.656613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:16:27Z"
kind: List
metadata:
  resourceVersion: ""