apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-178-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-178.ec2.internal
      uid: db4ec69b-f9d0-4e08-93fc-0692101257fc
    resourceVersion: "54177"
    uid: 2d11a89b-04a0-47ba-a20b-9200b540114d
  spec:
    sourcePod: network-check-source-6f8b768455-dsfdk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:22:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.196347ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:43:02Z"
    - latency: 1.031601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:42:02Z"
    - latency: 930.169µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:41:02Z"
    - latency: 1.055051ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:40:02Z"
    - latency: 1.067618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:39:02Z"
    - latency: 964.669µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:38:02Z"
    - latency: 1.151377ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:37:02Z"
    - latency: 904.303µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:36:02Z"
    - latency: 2.123613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:35:02Z"
    - latency: 1.005299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-178-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-178.ec2.internal
      uid: db4ec69b-f9d0-4e08-93fc-0692101257fc
    resourceVersion: "56166"
    uid: db91828e-c485-41ba-8550-3a9dea861f9c
  spec:
    sourcePod: network-check-source-6f8b768455-dsfdk
    targetEndpoint: a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:21:02Z"
      message: 'load-balancer-api-external: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.411679ms
      message: 'load-balancer-api-external: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:45:02Z"
    - latency: 8.871864ms
      message: 'load-balancer-api-external: resolved host name a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:45:02Z"
    - latency: 4.347951ms
      message: 'load-balancer-api-external: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:44:02Z"
    - latency: 8.285495ms
      message: 'load-balancer-api-external: resolved host name a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:44:02Z"
    - latency: 5.14581ms
      message: 'load-balancer-api-external: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:43:02Z"
    - latency: 8.926865ms
      message: 'load-balancer-api-external: resolved host name a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:43:02Z"
    - latency: 5.278518ms
      message: 'load-balancer-api-external: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:42:02Z"
    - latency: 8.101138ms
      message: 'load-balancer-api-external: resolved host name a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:42:02Z"
    - latency: 5.071186ms
      message: 'load-balancer-api-external: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:41:02Z"
    - latency: 14.793146ms
      message: 'load-balancer-api-external: resolved host name a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:41:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-178-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-178.ec2.internal
      uid: db4ec69b-f9d0-4e08-93fc-0692101257fc
    resourceVersion: "56167"
    uid: d040af7e-578a-4172-9952-dc039b0890c1
  spec:
    sourcePod: network-check-source-6f8b768455-dsfdk
    targetEndpoint: a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:21:02Z"
      message: 'load-balancer-api-internal: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.371662ms
      message: 'load-balancer-api-internal: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:45:02Z"
    - latency: 8.948791ms
      message: 'load-balancer-api-internal: resolved host name a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:45:02Z"
    - latency: 4.441901ms
      message: 'load-balancer-api-internal: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:44:02Z"
    - latency: 8.36932ms
      message: 'load-balancer-api-internal: resolved host name a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:44:02Z"
    - latency: 5.395951ms
      message: 'load-balancer-api-internal: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:43:02Z"
    - latency: 8.868047ms
      message: 'load-balancer-api-internal: resolved host name a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:43:02Z"
    - latency: 4.813956ms
      message: 'load-balancer-api-internal: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:42:02Z"
    - latency: 8.015009ms
      message: 'load-balancer-api-internal: resolved host name a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:42:02Z"
    - latency: 5.061214ms
      message: 'load-balancer-api-internal: tcp connection to a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:41:02Z"
    - latency: 14.709077ms
      message: 'load-balancer-api-internal: resolved host name a86ce6ab933584ebbb3440d3b9c89c1d-08e8eacf9000d218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:41:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-178-to-network-check-target-ip-10-0-131-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-178.ec2.internal
      uid: db4ec69b-f9d0-4e08-93fc-0692101257fc
    resourceVersion: "54174"
    uid: 68300746-8d4b-4a20-91d3-4ae0ba6e6f76
  spec:
    sourcePod: network-check-source-6f8b768455-dsfdk
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:22:02Z"
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 764.702µs
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:43:02Z"
    - latency: 769.474µs
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:42:02Z"
    - latency: 753.057µs
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:41:02Z"
    - latency: 921.743µs
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:40:02Z"
    - latency: 1.026481ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:39:02Z"
    - latency: 979.892µs
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:38:02Z"
    - latency: 1.564006ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:37:02Z"
    - latency: 838.741µs
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:36:02Z"
    - latency: 1.043612ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:35:02Z"
    - latency: 1.63742ms
      message: 'network-check-target-ip-10-0-131-178: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-178-to-network-check-target-ip-10-0-135-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-178.ec2.internal
      uid: db4ec69b-f9d0-4e08-93fc-0692101257fc
    resourceVersion: "54175"
    uid: 0fea4c6c-13aa-4895-b440-f139b07c0acc
  spec:
    sourcePod: network-check-source-6f8b768455-dsfdk
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:22:02Z"
      message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.419878ms
      message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:43:02Z"
    - latency: 2.258794ms
      message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:42:02Z"
    - latency: 2.22403ms
      message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:41:02Z"
    - latency: 2.700196ms
      message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:40:02Z"
    - latency: 2.612109ms
      message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:39:02Z"
    - latency: 1.942782ms
      message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:38:02Z"
    - latency: 2.537318ms
      message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:37:02Z"
    - latency: 2.359922ms
      message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:36:02Z"
    - latency: 2.472304ms
      message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:35:02Z"
    - latency: 2.012085ms
      message: 'network-check-target-ip-10-0-135-74: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-178-to-network-check-target-ip-10-0-141-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-178.ec2.internal
      uid: db4ec69b-f9d0-4e08-93fc-0692101257fc
    resourceVersion: "54176"
    uid: 45759c23-be8e-45c9-88b1-a00748addb2a
  spec:
    sourcePod: network-check-source-6f8b768455-dsfdk
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:22:02Z"
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.447446ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:43:02Z"
    - latency: 2.203207ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:42:02Z"
    - latency: 2.355822ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:41:02Z"
    - latency: 2.321558ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:40:02Z"
    - latency: 2.428966ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:39:02Z"
    - latency: 1.996169ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:38:02Z"
    - latency: 3.03986ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:37:02Z"
    - latency: 2.360466ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:36:02Z"
    - latency: 2.257801ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:35:02Z"
    - latency: 2.24019ms
      message: 'network-check-target-ip-10-0-141-146: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:15:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-178-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-178.ec2.internal
      uid: db4ec69b-f9d0-4e08-93fc-0692101257fc
    resourceVersion: "56165"
    uid: 24f47a8c-2571-4d92-8c25-2f94119f8792
  spec:
    sourcePod: network-check-source-6f8b768455-dsfdk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:21:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.265686ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:45:02Z"
    - latency: 2.099422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:45:02Z"
    - latency: 1.202533ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:44:02Z"
    - latency: 2.127232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:44:02Z"
    - latency: 849.436µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:43:02Z"
    - latency: 2.092372ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:43:02Z"
    - latency: 1.01951ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:42:02Z"
    - latency: 1.822439ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:42:02Z"
    - latency: 1.105683ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:41:02Z"
    - latency: 1.706677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:41:02Z"
kind: List
metadata:
  resourceVersion: ""