apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-109-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-109.ec2.internal
      uid: 4080ba46-5e66-4037-b348-499f2e8edc4b
    resourceVersion: "67851"
    uid: 1ab7738f-5592-4eb3-833a-04e147a1738e
  spec:
    sourcePod: network-check-source-6f8b768455-fzzll
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:05:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.012011ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:33:41Z"
    - latency: 1.080355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:32:41Z"
    - latency: 1.205542ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:31:41Z"
    - latency: 1.291454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:30:41Z"
    - latency: 972.168µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:29:41Z"
    - latency: 1.256529ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:28:41Z"
    - latency: 1.261129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:27:41Z"
    - latency: 1.504443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:26:41Z"
    - latency: 1.595136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:25:41Z"
    - latency: 1.491325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:24:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-109-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-109.ec2.internal
      uid: 4080ba46-5e66-4037-b348-499f2e8edc4b
    resourceVersion: "69084"
    uid: af045045-f918-40ef-85cf-86871931ef3c
  spec:
    sourcePod: network-check-source-6f8b768455-fzzll
    targetEndpoint: a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:04:41Z"
      message: 'load-balancer-api-external: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.572903ms
      message: 'load-balancer-api-external: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:34:41Z"
    - latency: 7.398308ms
      message: 'load-balancer-api-external: resolved host name a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:34:41Z"
    - latency: 5.991211ms
      message: 'load-balancer-api-external: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:33:41Z"
    - latency: 8.039137ms
      message: 'load-balancer-api-external: resolved host name a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:33:41Z"
    - latency: 5.379454ms
      message: 'load-balancer-api-external: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:32:41Z"
    - latency: 7.086586ms
      message: 'load-balancer-api-external: resolved host name a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:32:41Z"
    - latency: 4.466713ms
      message: 'load-balancer-api-external: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:31:41Z"
    - latency: 7.14684ms
      message: 'load-balancer-api-external: resolved host name a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:31:41Z"
    - latency: 5.70669ms
      message: 'load-balancer-api-external: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:30:41Z"
    - latency: 6.891203ms
      message: 'load-balancer-api-external: resolved host name a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:30:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-109-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-109.ec2.internal
      uid: 4080ba46-5e66-4037-b348-499f2e8edc4b
    resourceVersion: "69083"
    uid: 57dd9aa8-46d8-4bc1-9d9a-b118da35a2a6
  spec:
    sourcePod: network-check-source-6f8b768455-fzzll
    targetEndpoint: a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:04:41Z"
      message: 'load-balancer-api-internal: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.885542ms
      message: 'load-balancer-api-internal: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:34:41Z"
    - latency: 7.430409ms
      message: 'load-balancer-api-internal: resolved host name a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:34:41Z"
    - latency: 6.004137ms
      message: 'load-balancer-api-internal: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:33:41Z"
    - latency: 7.968553ms
      message: 'load-balancer-api-internal: resolved host name a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:33:41Z"
    - latency: 5.375151ms
      message: 'load-balancer-api-internal: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:32:41Z"
    - latency: 7.049247ms
      message: 'load-balancer-api-internal: resolved host name a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:32:41Z"
    - latency: 4.464774ms
      message: 'load-balancer-api-internal: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:31:41Z"
    - latency: 7.18266ms
      message: 'load-balancer-api-internal: resolved host name a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:31:41Z"
    - latency: 5.674626ms
      message: 'load-balancer-api-internal: tcp connection to a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:30:41Z"
    - latency: 6.853478ms
      message: 'load-balancer-api-internal: resolved host name a60b20453388f48b0b01571069718bcd-657d7f4c8c298ae5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:30:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-109-to-network-check-target-ip-10-0-128-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-109.ec2.internal
      uid: 4080ba46-5e66-4037-b348-499f2e8edc4b
    resourceVersion: "67850"
    uid: 664fde3b-cb39-4a0a-b3f5-0af006d97b16
  spec:
    sourcePod: network-check-source-6f8b768455-fzzll
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:05:41Z"
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.544498ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:33:41Z"
    - latency: 2.135221ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:32:41Z"
    - latency: 2.500275ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:31:41Z"
    - latency: 2.449669ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:30:41Z"
    - latency: 2.399514ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:29:41Z"
    - latency: 2.478963ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:28:41Z"
    - latency: 2.316391ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:27:41Z"
    - latency: 2.407108ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:26:41Z"
    - latency: 2.504373ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:25:41Z"
    - latency: 2.480268ms
      message: 'network-check-target-ip-10-0-128-29: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:24:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-109-to-network-check-target-ip-10-0-133-109
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-109.ec2.internal
      uid: 4080ba46-5e66-4037-b348-499f2e8edc4b
    resourceVersion: "67848"
    uid: dafe2d21-dba2-4c88-ba2e-2b23c4195662
  spec:
    sourcePod: network-check-source-6f8b768455-fzzll
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:05:41Z"
      message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.765µs
      message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:33:41Z"
    - latency: 1.400316ms
      message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:32:41Z"
    - latency: 954.332µs
      message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:31:41Z"
    - latency: 947.716µs
      message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:30:41Z"
    - latency: 996.668µs
      message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:29:41Z"
    - latency: 1.585924ms
      message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:28:41Z"
    - latency: 1.328096ms
      message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:27:41Z"
    - latency: 1.064412ms
      message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:26:41Z"
    - latency: 1.277326ms
      message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:25:41Z"
    - latency: 1.12747ms
      message: 'network-check-target-ip-10-0-133-109: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:24:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-109-to-network-check-target-ip-10-0-141-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-109.ec2.internal
      uid: 4080ba46-5e66-4037-b348-499f2e8edc4b
    resourceVersion: "67849"
    uid: f033192f-7555-46ef-b6db-aee8cd26ac79
  spec:
    sourcePod: network-check-source-6f8b768455-fzzll
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:05:41Z"
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.494338ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:33:41Z"
    - latency: 2.797566ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:32:41Z"
    - latency: 2.322585ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:31:41Z"
    - latency: 2.244626ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:30:41Z"
    - latency: 2.406647ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:29:41Z"
    - latency: 2.414582ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:28:41Z"
    - latency: 2.319035ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:27:41Z"
    - latency: 2.116458ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:26:41Z"
    - latency: 2.094311ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:25:41Z"
    - latency: 2.046516ms
      message: 'network-check-target-ip-10-0-141-255: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:24:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T17:58:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-109-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-109.ec2.internal
      uid: 4080ba46-5e66-4037-b348-499f2e8edc4b
    resourceVersion: "69082"
    uid: 3c9792ff-b9c5-49b7-8ead-0c6fe48bd9a5
  spec:
    sourcePod: network-check-source-6f8b768455-fzzll
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T18:04:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 881.562µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:34:41Z"
    - latency: 1.914855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:34:41Z"
    - latency: 934.756µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:33:41Z"
    - latency: 1.648482ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:33:41Z"
    - latency: 1.159031ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:32:41Z"
    - latency: 1.985936ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:32:41Z"
    - latency: 888.024µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:31:41Z"
    - latency: 1.786044ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:31:41Z"
    - latency: 1.152096ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T18:30:41Z"
    - latency: 1.86636ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T18:30:41Z"
kind: List
metadata:
  resourceVersion: ""