apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:31:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 53dd2d59-2afb-43c2-96f4-16f06ff26cb8
    resourceVersion: "56288"
    uid: 1087f1cf-5545-4c1a-a683-2cf4e284250b
  spec:
    sourcePod: network-check-source-989f8b8dc-6znrp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:38:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.175µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:20Z"
    - latency: 769.816µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:20Z"
    - latency: 900.125µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:20Z"
    - latency: 1.134749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:20Z"
    - latency: 1.089225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:20Z"
    - latency: 1.248139ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:20Z"
    - latency: 934.836µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:00:20Z"
    - latency: 950.714µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:59:20Z"
    - latency: 1.15952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:58:20Z"
    - latency: 926.42µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:31:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 53dd2d59-2afb-43c2-96f4-16f06ff26cb8
    resourceVersion: "57305"
    uid: abe17140-e450-48c7-b085-daa124d9fbe4
  spec:
    sourcePod: network-check-source-989f8b8dc-6znrp
    targetEndpoint: a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:37:20Z"
      message: 'load-balancer-api-external: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.409603ms
      message: 'load-balancer-api-external: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:20Z"
    - latency: 8.103899ms
      message: 'load-balancer-api-external: resolved host name a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:07:20Z"
    - latency: 5.606009ms
      message: 'load-balancer-api-external: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:20Z"
    - latency: 8.044565ms
      message: 'load-balancer-api-external: resolved host name a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:20Z"
    - latency: 4.473874ms
      message: 'load-balancer-api-external: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:20Z"
    - latency: 9.685477ms
      message: 'load-balancer-api-external: resolved host name a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:20Z"
    - latency: 5.144622ms
      message: 'load-balancer-api-external: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:20Z"
    - latency: 8.649432ms
      message: 'load-balancer-api-external: resolved host name a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:20Z"
    - latency: 6.233995ms
      message: 'load-balancer-api-external: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:20Z"
    - latency: 7.137163ms
      message: 'load-balancer-api-external: resolved host name a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:03:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:31:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 53dd2d59-2afb-43c2-96f4-16f06ff26cb8
    resourceVersion: "57306"
    uid: 4f9cf997-84ef-417c-848d-d69f1926e140
  spec:
    sourcePod: network-check-source-989f8b8dc-6znrp
    targetEndpoint: a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:37:20Z"
      message: 'load-balancer-api-internal: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.394746ms
      message: 'load-balancer-api-internal: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:20Z"
    - latency: 8.061231ms
      message: 'load-balancer-api-internal: resolved host name a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:07:20Z"
    - latency: 5.595571ms
      message: 'load-balancer-api-internal: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:20Z"
    - latency: 8.054788ms
      message: 'load-balancer-api-internal: resolved host name a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:20Z"
    - latency: 4.450963ms
      message: 'load-balancer-api-internal: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:20Z"
    - latency: 9.625652ms
      message: 'load-balancer-api-internal: resolved host name a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:20Z"
    - latency: 7.138162ms
      message: 'load-balancer-api-internal: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:20Z"
    - latency: 8.675079ms
      message: 'load-balancer-api-internal: resolved host name a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:20Z"
    - latency: 5.75061ms
      message: 'load-balancer-api-internal: tcp connection to a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:20Z"
    - latency: 7.05343ms
      message: 'load-balancer-api-internal: resolved host name a2c36976a23b34a6ea49b1185c5bbb99-959c7787d4eeffba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:03:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:31:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-network-check-target-ip-10-0-129-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 53dd2d59-2afb-43c2-96f4-16f06ff26cb8
    resourceVersion: "56287"
    uid: bea17af8-5e3e-4a0a-b813-cde4f077560d
  spec:
    sourcePod: network-check-source-989f8b8dc-6znrp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:38:20Z"
      message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.145053ms
      message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:20Z"
    - latency: 1.937985ms
      message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:20Z"
    - latency: 1.85952ms
      message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:20Z"
    - latency: 2.15408ms
      message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:20Z"
    - latency: 2.051186ms
      message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:20Z"
    - latency: 1.878286ms
      message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:20Z"
    - latency: 2.038146ms
      message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:00:20Z"
    - latency: 2.053124ms
      message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:59:20Z"
    - latency: 1.822029ms
      message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:58:20Z"
    - latency: 2.008449ms
      message: 'network-check-target-ip-10-0-129-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:31:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-network-check-target-ip-10-0-140-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 53dd2d59-2afb-43c2-96f4-16f06ff26cb8
    resourceVersion: "56286"
    uid: aac2f131-9483-4e06-bc6e-f2dd7a4f081b
  spec:
    sourcePod: network-check-source-989f8b8dc-6znrp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:38:20Z"
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.282404ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:20Z"
    - latency: 2.097549ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:20Z"
    - latency: 1.794016ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:20Z"
    - latency: 1.677154ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:20Z"
    - latency: 1.758423ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:20Z"
    - latency: 2.176887ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:20Z"
    - latency: 1.856275ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:00:20Z"
    - latency: 2.527894ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:59:20Z"
    - latency: 1.872969ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:58:20Z"
    - latency: 1.686039ms
      message: 'network-check-target-ip-10-0-140-28: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:31:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-network-check-target-ip-10-0-142-74
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 53dd2d59-2afb-43c2-96f4-16f06ff26cb8
    resourceVersion: "56285"
    uid: 5fbc84c8-5cd0-4f68-b1db-be4cc7c714ce
  spec:
    sourcePod: network-check-source-989f8b8dc-6znrp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:38:20Z"
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.896µs
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:20Z"
    - latency: 1.118417ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:20Z"
    - latency: 1.144886ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:20Z"
    - latency: 916.86µs
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:20Z"
    - latency: 762.694µs
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:02:20Z"
    - latency: 824.442µs
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:01:20Z"
    - latency: 868.332µs
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:00:20Z"
    - latency: 1.475182ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:59:20Z"
    - latency: 724.369µs
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:58:20Z"
    - latency: 1.199999ms
      message: 'network-check-target-ip-10-0-142-74: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T16:57:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:31:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-74-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-74.ec2.internal
      uid: 53dd2d59-2afb-43c2-96f4-16f06ff26cb8
    resourceVersion: "57304"
    uid: e581ffc0-e051-4fa5-a43b-c62224e69b1d
  spec:
    sourcePod: network-check-source-989f8b8dc-6znrp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:37:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 818.534µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:07:20Z"
    - latency: 1.872222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:07:20Z"
    - latency: 914.613µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:06:20Z"
    - latency: 2.047699ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:06:20Z"
    - latency: 909.829µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:05:20Z"
    - latency: 2.616254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:05:20Z"
    - latency: 1.043912ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:04:20Z"
    - latency: 1.867927ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:04:20Z"
    - latency: 845.963µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:03:20Z"
    - latency: 2.407237ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:03:20Z"
kind: List
metadata:
  resourceVersion: ""