apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:46:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-97-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-97.ec2.internal
      uid: d81569c2-aeed-4502-a9c4-bb274027e595
    resourceVersion: "50008"
    uid: 14b93e1d-17ca-4703-bc9a-1feacf55beef
  spec:
    sourcePod: network-check-source-dbd9cf844-29wzh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:53:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.034234ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:21:59Z"
    - latency: 1.244819ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:20:59Z"
    - latency: 994.605µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:19:59Z"
    - latency: 1.509281ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:18:59Z"
    - latency: 1.002537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:17:59Z"
    - latency: 916.501µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:16:59Z"
    - latency: 1.054767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:15:59Z"
    - latency: 1.273183ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:14:59Z"
    - latency: 1.159379ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:13:59Z"
    - latency: 933.499µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:12:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:46:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-97-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-97.ec2.internal
      uid: d81569c2-aeed-4502-a9c4-bb274027e595
    resourceVersion: "51097"
    uid: 0a5f335e-e95c-4601-b0a2-7404787acd71
  spec:
    sourcePod: network-check-source-dbd9cf844-29wzh
    targetEndpoint: a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:52:59Z"
      message: 'load-balancer-api-external: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.627822ms
      message: 'load-balancer-api-external: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:22:59Z"
    - latency: 7.412281ms
      message: 'load-balancer-api-external: resolved host name a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:22:59Z"
    - latency: 4.691063ms
      message: 'load-balancer-api-external: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:21:59Z"
    - latency: 7.039475ms
      message: 'load-balancer-api-external: resolved host name a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:21:59Z"
    - latency: 4.043861ms
      message: 'load-balancer-api-external: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:20:59Z"
    - latency: 7.731473ms
      message: 'load-balancer-api-external: resolved host name a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:20:59Z"
    - latency: 4.483913ms
      message: 'load-balancer-api-external: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:19:59Z"
    - latency: 7.251123ms
      message: 'load-balancer-api-external: resolved host name a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:19:59Z"
    - latency: 4.780445ms
      message: 'load-balancer-api-external: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:18:59Z"
    - latency: 7.199021ms
      message: 'load-balancer-api-external: resolved host name a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:18:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:46:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-97-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-97.ec2.internal
      uid: d81569c2-aeed-4502-a9c4-bb274027e595
    resourceVersion: "51098"
    uid: 10f0ee15-402e-4321-8503-e7465d965da2
  spec:
    sourcePod: network-check-source-dbd9cf844-29wzh
    targetEndpoint: a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:52:59Z"
      message: 'load-balancer-api-internal: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.61151ms
      message: 'load-balancer-api-internal: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:22:59Z"
    - latency: 7.512634ms
      message: 'load-balancer-api-internal: resolved host name a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:22:59Z"
    - latency: 4.839427ms
      message: 'load-balancer-api-internal: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:21:59Z"
    - latency: 6.955888ms
      message: 'load-balancer-api-internal: resolved host name a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:21:59Z"
    - latency: 4.032036ms
      message: 'load-balancer-api-internal: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:20:59Z"
    - latency: 7.90198ms
      message: 'load-balancer-api-internal: resolved host name a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:20:59Z"
    - latency: 6.220209ms
      message: 'load-balancer-api-internal: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:19:59Z"
    - latency: 7.174587ms
      message: 'load-balancer-api-internal: resolved host name a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:19:59Z"
    - latency: 4.192977ms
      message: 'load-balancer-api-internal: tcp connection to a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:18:59Z"
    - latency: 7.269656ms
      message: 'load-balancer-api-internal: resolved host name a441becad7978476ba197279a61d0cb4-d7281abd42967002.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:18:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:46:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-97-to-network-check-target-ip-10-0-130-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-97.ec2.internal
      uid: d81569c2-aeed-4502-a9c4-bb274027e595
    resourceVersion: "50006"
    uid: d28f0e98-037e-4fca-b698-6e47caec45ee
  spec:
    sourcePod: network-check-source-dbd9cf844-29wzh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:53:59Z"
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.949085ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:21:59Z"
    - latency: 1.967519ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:20:59Z"
    - latency: 2.049628ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:19:59Z"
    - latency: 1.537971ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:18:59Z"
    - latency: 1.681175ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:17:59Z"
    - latency: 1.810713ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:16:59Z"
    - latency: 1.973279ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:15:59Z"
    - latency: 1.699404ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:14:59Z"
    - latency: 1.664937ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:13:59Z"
    - latency: 1.87637ms
      message: 'network-check-target-ip-10-0-130-142: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:12:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:46:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-97-to-network-check-target-ip-10-0-135-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-97.ec2.internal
      uid: d81569c2-aeed-4502-a9c4-bb274027e595
    resourceVersion: "50007"
    uid: e54b31c3-9600-4781-b959-8f3025e16e5a
  spec:
    sourcePod: network-check-source-dbd9cf844-29wzh
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:53:59Z"
      message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.364891ms
      message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:21:59Z"
    - latency: 2.384449ms
      message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:20:59Z"
    - latency: 2.319209ms
      message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:19:59Z"
    - latency: 2.162062ms
      message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:18:59Z"
    - latency: 2.051892ms
      message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:17:59Z"
    - latency: 2.385946ms
      message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:16:59Z"
    - latency: 2.034111ms
      message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:15:59Z"
    - latency: 1.804671ms
      message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:14:59Z"
    - latency: 2.112363ms
      message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:13:59Z"
    - latency: 2.113172ms
      message: 'network-check-target-ip-10-0-135-133: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:12:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:46:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-97-to-network-check-target-ip-10-0-135-97
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-97.ec2.internal
      uid: d81569c2-aeed-4502-a9c4-bb274027e595
    resourceVersion: "50005"
    uid: 0d14e7ec-c1a1-4344-8851-5f2413c12098
  spec:
    sourcePod: network-check-source-dbd9cf844-29wzh
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:53:59Z"
      message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.004302ms
      message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:21:59Z"
    - latency: 904.608µs
      message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:20:59Z"
    - latency: 1.169212ms
      message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:19:59Z"
    - latency: 978.691µs
      message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:18:59Z"
    - latency: 1.032757ms
      message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:17:59Z"
    - latency: 1.152053ms
      message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:16:59Z"
    - latency: 1.034235ms
      message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:15:59Z"
    - latency: 1.398593ms
      message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:14:59Z"
    - latency: 838.025µs
      message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:13:59Z"
    - latency: 1.324261ms
      message: 'network-check-target-ip-10-0-135-97: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:12:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-05T15:46:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-97-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-97.ec2.internal
      uid: d81569c2-aeed-4502-a9c4-bb274027e595
    resourceVersion: "51096"
    uid: 28159a08-a4e5-4e46-92f2-3d5d186a7832
  spec:
    sourcePod: network-check-source-dbd9cf844-29wzh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-05T15:52:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.208703ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:22:59Z"
    - latency: 1.784066ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:22:59Z"
    - latency: 1.298727ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:21:59Z"
    - latency: 2.033561ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:21:59Z"
    - latency: 1.208412ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:20:59Z"
    - latency: 2.282712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:20:59Z"
    - latency: 1.312879ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:19:59Z"
    - latency: 1.887235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:19:59Z"
    - latency: 1.242912ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-05T16:18:59Z"
    - latency: 2.079842ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-05T16:18:59Z"
kind: List
metadata:
  resourceVersion: ""