apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:44:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-81-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-81.ec2.internal
      uid: c2ef1543-d627-42cf-bfd5-b5b4eb723de8
    resourceVersion: "87887"
    uid: 3886e232-0575-4d1e-bd45-6f15f0d01d51
  spec:
    sourcePod: network-check-source-6f8b768455-hz77x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:51:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.147848ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:54:06Z"
    - latency: 1.190104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:53:06Z"
    - latency: 1.098607ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:52:06Z"
    - latency: 1.356194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:51:06Z"
    - latency: 865.157µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:50:06Z"
    - latency: 1.016265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:49:06Z"
    - latency: 1.178718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:48:06Z"
    - latency: 1.69036ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:47:06Z"
    - latency: 1.19693ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:46:06Z"
    - latency: 924.587µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:45:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:44:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-81-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-81.ec2.internal
      uid: c2ef1543-d627-42cf-bfd5-b5b4eb723de8
    resourceVersion: "89978"
    uid: 937373da-9a71-4727-a556-ee624633d67a
  spec:
    sourcePod: network-check-source-6f8b768455-hz77x
    targetEndpoint: a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:50:06Z"
      message: 'load-balancer-api-external: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.770889ms
      message: 'load-balancer-api-external: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:56:06Z"
    - latency: 8.412083ms
      message: 'load-balancer-api-external: resolved host name a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:56:06Z"
    - latency: 7.51132ms
      message: 'load-balancer-api-external: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:55:06Z"
    - latency: 9.202131ms
      message: 'load-balancer-api-external: resolved host name a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:55:06Z"
    - latency: 5.240032ms
      message: 'load-balancer-api-external: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:54:06Z"
    - latency: 9.383551ms
      message: 'load-balancer-api-external: resolved host name a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:54:06Z"
    - latency: 4.008067ms
      message: 'load-balancer-api-external: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:53:06Z"
    - latency: 14.053163ms
      message: 'load-balancer-api-external: resolved host name a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:53:06Z"
    - latency: 4.418541ms
      message: 'load-balancer-api-external: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:52:06Z"
    - latency: 8.245322ms
      message: 'load-balancer-api-external: resolved host name a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:52:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:44:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-81-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-81.ec2.internal
      uid: c2ef1543-d627-42cf-bfd5-b5b4eb723de8
    resourceVersion: "89979"
    uid: 14eb9c58-7e83-481b-8429-f6e5a65b3065
  spec:
    sourcePod: network-check-source-6f8b768455-hz77x
    targetEndpoint: a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:50:06Z"
      message: 'load-balancer-api-internal: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.111549ms
      message: 'load-balancer-api-internal: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:56:06Z"
    - latency: 8.520251ms
      message: 'load-balancer-api-internal: resolved host name a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:56:06Z"
    - latency: 6.658091ms
      message: 'load-balancer-api-internal: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:55:06Z"
    - latency: 9.398183ms
      message: 'load-balancer-api-internal: resolved host name a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:55:06Z"
    - latency: 5.250784ms
      message: 'load-balancer-api-internal: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:54:06Z"
    - latency: 9.449424ms
      message: 'load-balancer-api-internal: resolved host name a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:54:06Z"
    - latency: 4.011798ms
      message: 'load-balancer-api-internal: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:53:06Z"
    - latency: 14.118832ms
      message: 'load-balancer-api-internal: resolved host name a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:53:06Z"
    - latency: 4.395895ms
      message: 'load-balancer-api-internal: tcp connection to a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:52:06Z"
    - latency: 8.211081ms
      message: 'load-balancer-api-internal: resolved host name a7bfb1051cc0e4458950159986866a4f-53a45b6d33073246.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:52:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:44:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-81-to-network-check-target-ip-10-0-136-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-81.ec2.internal
      uid: c2ef1543-d627-42cf-bfd5-b5b4eb723de8
    resourceVersion: "87886"
    uid: c91a7775-d581-4044-937d-1e5bbc90f9cf
  spec:
    sourcePod: network-check-source-6f8b768455-hz77x
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:51:06Z"
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.161101ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:54:06Z"
    - latency: 2.139448ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:53:06Z"
    - latency: 2.379266ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:52:06Z"
    - latency: 2.224014ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:51:06Z"
    - latency: 2.007001ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:50:06Z"
    - latency: 8.17518ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:49:06Z"
    - latency: 2.710572ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:48:06Z"
    - latency: 2.278388ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:47:06Z"
    - latency: 2.102298ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:46:06Z"
    - latency: 2.046133ms
      message: 'network-check-target-ip-10-0-136-120: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:45:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:44:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-81-to-network-check-target-ip-10-0-139-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-81.ec2.internal
      uid: c2ef1543-d627-42cf-bfd5-b5b4eb723de8
    resourceVersion: "87884"
    uid: 4ef6aa14-982e-43bc-8995-bd5a433db1eb
  spec:
    sourcePod: network-check-source-6f8b768455-hz77x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:51:06Z"
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 720.35µs
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:54:06Z"
    - latency: 931.243µs
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:53:06Z"
    - latency: 931.574µs
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:52:06Z"
    - latency: 1.274717ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:51:06Z"
    - latency: 1.480774ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:50:06Z"
    - latency: 1.064577ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:49:06Z"
    - latency: 799.744µs
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:48:06Z"
    - latency: 764.583µs
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:47:06Z"
    - latency: 1.204469ms
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:46:06Z"
    - latency: 859.492µs
      message: 'network-check-target-ip-10-0-139-81: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:45:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:44:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-81-to-network-check-target-ip-10-0-141-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-81.ec2.internal
      uid: c2ef1543-d627-42cf-bfd5-b5b4eb723de8
    resourceVersion: "87885"
    uid: 6bcdf67c-3bcf-4e78-bbd4-10d9d973dd4d
  spec:
    sourcePod: network-check-source-6f8b768455-hz77x
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:51:06Z"
      message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.44702ms
      message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:54:06Z"
    - latency: 2.508936ms
      message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:53:06Z"
    - latency: 2.48388ms
      message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:52:06Z"
    - latency: 2.937866ms
      message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:51:06Z"
    - latency: 2.405407ms
      message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:50:06Z"
    - latency: 6.390962ms
      message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:49:06Z"
    - latency: 2.741639ms
      message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:48:06Z"
    - latency: 2.378894ms
      message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:47:06Z"
    - latency: 2.702908ms
      message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:46:06Z"
    - latency: 2.045844ms
      message: 'network-check-target-ip-10-0-141-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:45:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T19:44:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-81-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-81.ec2.internal
      uid: c2ef1543-d627-42cf-bfd5-b5b4eb723de8
    resourceVersion: "89977"
    uid: de738828-75ce-4410-a1de-ecaf28ebf6e3
  spec:
    sourcePod: network-check-source-6f8b768455-hz77x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T19:50:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 795.239µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:56:06Z"
    - latency: 2.059889ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:56:06Z"
    - latency: 799.64µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:55:06Z"
    - latency: 1.902177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:55:06Z"
    - latency: 1.268383ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:54:06Z"
    - latency: 1.647626ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:54:06Z"
    - latency: 1.15783ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:53:06Z"
    - latency: 1.787544ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:53:06Z"
    - latency: 1.10531ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T20:52:06Z"
    - latency: 1.787804ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T20:52:06Z"
kind: List
metadata:
  resourceVersion: ""