apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T16:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: ea9dc8fa-4656-48a1-a75a-e62497763294
    resourceVersion: "83112"
    uid: 206839cd-c099-4ba2-920a-237e27d93d75
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5cfd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T16:18:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.204333ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T17:00:42Z"
    - latency: 1.228254ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:59:42Z"
    - latency: 991.716µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:58:42Z"
    - latency: 1.200561ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:57:42Z"
    - latency: 1.202479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:56:42Z"
    - latency: 1.126851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:55:42Z"
    - latency: 1.06918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:54:42Z"
    - latency: 1.174618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:53:42Z"
    - latency: 1.107714ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:52:42Z"
    - latency: 1.218407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T16:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: ea9dc8fa-4656-48a1-a75a-e62497763294
    resourceVersion: "80614"
    uid: 6fd43076-0aee-45ea-a2a8-e1075bb6168b
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5cfd
    targetEndpoint: ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T16:17:42Z"
      message: 'load-balancer-api-external: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.476354ms
      message: 'load-balancer-api-external: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:59:42Z"
    - latency: 6.599016ms
      message: 'load-balancer-api-external: resolved host name ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:59:42Z"
    - latency: 3.815089ms
      message: 'load-balancer-api-external: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:58:42Z"
    - latency: 6.668049ms
      message: 'load-balancer-api-external: resolved host name ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:58:42Z"
    - latency: 4.147417ms
      message: 'load-balancer-api-external: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:57:42Z"
    - latency: 7.558705ms
      message: 'load-balancer-api-external: resolved host name ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:57:42Z"
    - latency: 3.48825ms
      message: 'load-balancer-api-external: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:56:42Z"
    - latency: 6.788291ms
      message: 'load-balancer-api-external: resolved host name ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:56:42Z"
    - latency: 5.519242ms
      message: 'load-balancer-api-external: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:55:42Z"
    - latency: 7.156928ms
      message: 'load-balancer-api-external: resolved host name ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T16:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: ea9dc8fa-4656-48a1-a75a-e62497763294
    resourceVersion: "80613"
    uid: bed18262-f239-43ea-972c-da9ec8823ff1
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5cfd
    targetEndpoint: ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T16:17:42Z"
      message: 'load-balancer-api-internal: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.520039ms
      message: 'load-balancer-api-internal: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:59:42Z"
    - latency: 6.6697ms
      message: 'load-balancer-api-internal: resolved host name ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:59:42Z"
    - latency: 3.8275ms
      message: 'load-balancer-api-internal: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:58:42Z"
    - latency: 6.724975ms
      message: 'load-balancer-api-internal: resolved host name ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:58:42Z"
    - latency: 3.838268ms
      message: 'load-balancer-api-internal: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:57:42Z"
    - latency: 7.597682ms
      message: 'load-balancer-api-internal: resolved host name ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:57:42Z"
    - latency: 3.819913ms
      message: 'load-balancer-api-internal: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:56:42Z"
    - latency: 6.820808ms
      message: 'load-balancer-api-internal: resolved host name ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:56:42Z"
    - latency: 5.482058ms
      message: 'load-balancer-api-internal: tcp connection to ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:55:42Z"
    - latency: 7.22069ms
      message: 'load-balancer-api-internal: resolved host name ae828b8e596ab4e1aad3672a98e564f0-7a89874b9e88d6bc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:55:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T16:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-network-check-target-ip-10-0-130-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: ea9dc8fa-4656-48a1-a75a-e62497763294
    resourceVersion: "83110"
    uid: c0b33707-5700-4413-a12f-bdf65128848a
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5cfd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T16:18:42Z"
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.381386ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T17:00:42Z"
    - latency: 2.577457ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:59:42Z"
    - latency: 2.158495ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:58:42Z"
    - latency: 2.241338ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:57:42Z"
    - latency: 2.57806ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:56:42Z"
    - latency: 2.591134ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:55:42Z"
    - latency: 2.539246ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:54:42Z"
    - latency: 2.598791ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:53:42Z"
    - latency: 2.25353ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:52:42Z"
    - latency: 2.121356ms
      message: 'network-check-target-ip-10-0-130-70: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T16:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-network-check-target-ip-10-0-131-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: ea9dc8fa-4656-48a1-a75a-e62497763294
    resourceVersion: "83111"
    uid: 2eb0cbde-b0d3-4e3c-bb85-d6357143778a
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5cfd
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T16:18:42Z"
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.382623ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T17:00:42Z"
    - latency: 939.486µs
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:59:42Z"
    - latency: 1.146334ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:58:42Z"
    - latency: 897.623µs
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:57:42Z"
    - latency: 969.871µs
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:56:42Z"
    - latency: 1.561891ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:55:42Z"
    - latency: 1.45779ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:54:42Z"
    - latency: 1.047109ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:53:42Z"
    - latency: 1.450334ms
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:52:42Z"
    - latency: 974.89µs
      message: 'network-check-target-ip-10-0-131-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T16:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-network-check-target-ip-10-0-135-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: ea9dc8fa-4656-48a1-a75a-e62497763294
    resourceVersion: "83109"
    uid: 8608a633-023c-43f3-920d-199aedec2541
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5cfd
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T16:18:42Z"
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.448624ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T17:00:42Z"
    - latency: 2.310139ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:59:42Z"
    - latency: 2.414305ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:58:42Z"
    - latency: 2.065677ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:57:42Z"
    - latency: 2.500045ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:56:42Z"
    - latency: 2.328289ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:55:42Z"
    - latency: 2.623394ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:54:42Z"
    - latency: 2.257687ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:53:42Z"
    - latency: 2.224094ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:52:42Z"
    - latency: 2.234491ms
      message: 'network-check-target-ip-10-0-135-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:51:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-26T16:11:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-99.ec2.internal
      uid: ea9dc8fa-4656-48a1-a75a-e62497763294
    resourceVersion: "80612"
    uid: 8069bf58-e3a9-4e15-8b89-38e267c99f2a
  spec:
    sourcePod: network-check-source-7d88cb55d8-q5cfd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-26T16:17:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 921.918µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:59:42Z"
    - latency: 1.924252ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:59:42Z"
    - latency: 872.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:58:42Z"
    - latency: 2.023808ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:58:42Z"
    - latency: 874.742µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:57:42Z"
    - latency: 1.966315ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:57:42Z"
    - latency: 900.771µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:56:42Z"
    - latency: 1.795324ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:56:42Z"
    - latency: 1.123894ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-26T16:55:42Z"
    - latency: 2.181357ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-26T16:55:42Z"
kind: List
metadata:
  resourceVersion: ""