apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:04:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: f19ee4a5-8969-4cd3-963a-8c0d623240f1
    resourceVersion: "58822"
    uid: 2a805769-6f97-473d-bae4-e2928658d1d4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lhczq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:11:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.466µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:46:58Z"
    - latency: 970.707µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:45:58Z"
    - latency: 1.100216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:44:58Z"
    - latency: 909.589µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:43:58Z"
    - latency: 965.828µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:42:58Z"
    - latency: 1.021387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:41:58Z"
    - latency: 922.807µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:40:58Z"
    - latency: 858.336µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:39:58Z"
    - latency: 1.42189ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:38:58Z"
    - latency: 1.436692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:37:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:04:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: f19ee4a5-8969-4cd3-963a-8c0d623240f1
    resourceVersion: "58824"
    uid: c6dffd35-ce02-46bc-9ff6-0c66350719b2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lhczq
    targetEndpoint: adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:10:58Z"
      message: 'load-balancer-api-external: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.479436ms
      message: 'load-balancer-api-external: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:46:58Z"
    - latency: 11.615488ms
      message: 'load-balancer-api-external: resolved host name adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:46:58Z"
    - latency: 5.320337ms
      message: 'load-balancer-api-external: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:45:58Z"
    - latency: 8.431385ms
      message: 'load-balancer-api-external: resolved host name adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:45:58Z"
    - latency: 5.910816ms
      message: 'load-balancer-api-external: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:44:58Z"
    - latency: 8.628958ms
      message: 'load-balancer-api-external: resolved host name adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:44:58Z"
    - latency: 3.366617ms
      message: 'load-balancer-api-external: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:43:58Z"
    - latency: 8.046909ms
      message: 'load-balancer-api-external: resolved host name adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:43:58Z"
    - latency: 3.38189ms
      message: 'load-balancer-api-external: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:42:58Z"
    - latency: 9.009608ms
      message: 'load-balancer-api-external: resolved host name adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:42:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:04:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: f19ee4a5-8969-4cd3-963a-8c0d623240f1
    resourceVersion: "58823"
    uid: 85bc2d99-5a78-45f8-ae79-526959573791
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lhczq
    targetEndpoint: adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:10:58Z"
      message: 'load-balancer-api-internal: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.759055ms
      message: 'load-balancer-api-internal: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:46:58Z"
    - latency: 11.651871ms
      message: 'load-balancer-api-internal: resolved host name adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:46:58Z"
    - latency: 5.32465ms
      message: 'load-balancer-api-internal: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:45:58Z"
    - latency: 8.346327ms
      message: 'load-balancer-api-internal: resolved host name adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:45:58Z"
    - latency: 5.754854ms
      message: 'load-balancer-api-internal: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:44:58Z"
    - latency: 8.50697ms
      message: 'load-balancer-api-internal: resolved host name adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:44:58Z"
    - latency: 5.44856ms
      message: 'load-balancer-api-internal: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:43:58Z"
    - latency: 8.018083ms
      message: 'load-balancer-api-internal: resolved host name adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:43:58Z"
    - latency: 3.943436ms
      message: 'load-balancer-api-internal: tcp connection to adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:42:58Z"
    - latency: 8.945478ms
      message: 'load-balancer-api-internal: resolved host name adbd00807e7354da69f715192295c390-ae4b5e108933233d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:42:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:04:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-network-check-target-ip-10-0-133-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: f19ee4a5-8969-4cd3-963a-8c0d623240f1
    resourceVersion: "58818"
    uid: 348310de-d6f6-4ee0-aa1f-71e35289b5bd
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lhczq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:11:58Z"
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.347523ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:46:58Z"
    - latency: 1.954122ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:45:58Z"
    - latency: 2.348784ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:44:58Z"
    - latency: 2.286537ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:43:58Z"
    - latency: 2.25006ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:42:58Z"
    - latency: 2.323392ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:41:58Z"
    - latency: 2.112137ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:40:58Z"
    - latency: 2.556208ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:39:58Z"
    - latency: 2.135646ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:38:58Z"
    - latency: 2.202222ms
      message: 'network-check-target-ip-10-0-133-217: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:37:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:04:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-network-check-target-ip-10-0-139-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: f19ee4a5-8969-4cd3-963a-8c0d623240f1
    resourceVersion: "58817"
    uid: c3b7c03c-e2bb-4274-a8f8-14a2a6c4fa7d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lhczq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:11:58Z"
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.104955ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:46:58Z"
    - latency: 1.397842ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:45:58Z"
    - latency: 1.041124ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:44:58Z"
    - latency: 864.053µs
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:43:58Z"
    - latency: 887.594µs
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:42:58Z"
    - latency: 974.421µs
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:41:58Z"
    - latency: 863.338µs
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:40:58Z"
    - latency: 1.0624ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:39:58Z"
    - latency: 846.595µs
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:38:58Z"
    - latency: 1.655337ms
      message: 'network-check-target-ip-10-0-139-2: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:37:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:04:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-network-check-target-ip-10-0-142-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: f19ee4a5-8969-4cd3-963a-8c0d623240f1
    resourceVersion: "58821"
    uid: 7cffbf81-d9fb-4333-87e0-c03413d0c9c8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lhczq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:11:58Z"
      message: 'network-check-target-ip-10-0-142-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.464696ms
      message: 'network-check-target-ip-10-0-142-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:46:58Z"
    - latency: 2.668245ms
      message: 'network-check-target-ip-10-0-142-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:45:58Z"
    - latency: 2.246317ms
      message: 'network-check-target-ip-10-0-142-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:44:58Z"
    - latency: 2.069172ms
      message: 'network-check-target-ip-10-0-142-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:43:58Z"
    - latency: 2.134904ms
      message: 'network-check-target-ip-10-0-142-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:42:58Z"
    - latency: 2.380396ms
      message: 'network-check-target-ip-10-0-142-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:41:58Z"
    - latency: 2.272599ms
      message: 'network-check-target-ip-10-0-142-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:40:58Z"
    - latency: 2.255734ms
      message: 'network-check-target-ip-10-0-142-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:39:58Z"
    - latency: 1.982741ms
      message: 'network-check-target-ip-10-0-142-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:38:58Z"
    - latency: 2.581314ms
      message: 'network-check-target-ip-10-0-142-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:37:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-23T15:04:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-2-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-2.ec2.internal
      uid: f19ee4a5-8969-4cd3-963a-8c0d623240f1
    resourceVersion: "58820"
    uid: e6f67eb4-cb1f-465c-be71-7e4cb9192b37
  spec:
    sourcePod: network-check-source-7bc5b6bf85-lhczq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-23T15:10:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.456µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:46:58Z"
    - latency: 2.489786ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:46:58Z"
    - latency: 1.012693ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:45:58Z"
    - latency: 1.971942ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:45:58Z"
    - latency: 1.120768ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:44:58Z"
    - latency: 1.762021ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:44:58Z"
    - latency: 757.64µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:43:58Z"
    - latency: 1.608634ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:43:58Z"
    - latency: 678.189µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-23T15:42:58Z"
    - latency: 2.19201ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-23T15:42:58Z"
kind: List
metadata:
  resourceVersion: ""