apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-172-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-172.ec2.internal
      uid: ac90309c-2da7-475b-83be-92bc58cd322a
    resourceVersion: "54545"
    uid: 2b77ee81-de1f-43b9-8890-39ab180743c6
  spec:
    sourcePod: network-check-source-989f8b8dc-79r5t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:58:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 879.035µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:47Z"
    - latency: 1.209952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:47Z"
    - latency: 2.62263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:47Z"
    - latency: 1.031107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:47Z"
    - latency: 1.481768ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:22:47Z"
    - latency: 5.080397ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:21:47Z"
    - latency: 988.852µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:20:47Z"
    - latency: 1.179505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:19:47Z"
    - latency: 953.445µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:18:47Z"
    - latency: 867.495µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:17:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-172-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-172.ec2.internal
      uid: ac90309c-2da7-475b-83be-92bc58cd322a
    resourceVersion: "55469"
    uid: 3fdb55f0-183a-4470-b6ed-140d2ea66de3
  spec:
    sourcePod: network-check-source-989f8b8dc-79r5t
    targetEndpoint: a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:57:47Z"
      message: 'load-balancer-api-external: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.846057ms
      message: 'load-balancer-api-external: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:47Z"
    - latency: 6.582781ms
      message: 'load-balancer-api-external: resolved host name a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:27:47Z"
    - latency: 5.319682ms
      message: 'load-balancer-api-external: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:47Z"
    - latency: 7.037786ms
      message: 'load-balancer-api-external: resolved host name a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:26:47Z"
    - latency: 4.717926ms
      message: 'load-balancer-api-external: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:47Z"
    - latency: 7.693214ms
      message: 'load-balancer-api-external: resolved host name a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:25:47Z"
    - latency: 5.406891ms
      message: 'load-balancer-api-external: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:47Z"
    - latency: 9.511593ms
      message: 'load-balancer-api-external: resolved host name a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:24:47Z"
    - latency: 4.595114ms
      message: 'load-balancer-api-external: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:47Z"
    - latency: 8.22385ms
      message: 'load-balancer-api-external: resolved host name a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:23:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-172-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-172.ec2.internal
      uid: ac90309c-2da7-475b-83be-92bc58cd322a
    resourceVersion: "55468"
    uid: 84fa3c77-c383-48f1-9898-c0fe411e0515
  spec:
    sourcePod: network-check-source-989f8b8dc-79r5t
    targetEndpoint: a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:57:47Z"
      message: 'load-balancer-api-internal: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.963746ms
      message: 'load-balancer-api-internal: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:47Z"
    - latency: 6.617086ms
      message: 'load-balancer-api-internal: resolved host name a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:27:47Z"
    - latency: 5.331979ms
      message: 'load-balancer-api-internal: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:47Z"
    - latency: 7.001593ms
      message: 'load-balancer-api-internal: resolved host name a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:26:47Z"
    - latency: 4.682775ms
      message: 'load-balancer-api-internal: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:47Z"
    - latency: 7.712046ms
      message: 'load-balancer-api-internal: resolved host name a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:25:47Z"
    - latency: 5.353185ms
      message: 'load-balancer-api-internal: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:47Z"
    - latency: 9.586389ms
      message: 'load-balancer-api-internal: resolved host name a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:24:47Z"
    - latency: 3.669512ms
      message: 'load-balancer-api-internal: tcp connection to a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:47Z"
    - latency: 8.187373ms
      message: 'load-balancer-api-internal: resolved host name a0f4f57ee175746a7b1089505098b461-6b9c4bb55bebd02e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:23:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-172-to-network-check-target-ip-10-0-130-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-172.ec2.internal
      uid: ac90309c-2da7-475b-83be-92bc58cd322a
    resourceVersion: "54542"
    uid: c975ac0c-f921-4162-a445-c872d929db69
  spec:
    sourcePod: network-check-source-989f8b8dc-79r5t
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:58:47Z"
      message: 'network-check-target-ip-10-0-130-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.391426ms
      message: 'network-check-target-ip-10-0-130-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:47Z"
    - latency: 1.729924ms
      message: 'network-check-target-ip-10-0-130-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:47Z"
    - latency: 2.173363ms
      message: 'network-check-target-ip-10-0-130-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:47Z"
    - latency: 1.644677ms
      message: 'network-check-target-ip-10-0-130-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:47Z"
    - latency: 1.089831ms
      message: 'network-check-target-ip-10-0-130-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:22:47Z"
    - latency: 5.465833ms
      message: 'network-check-target-ip-10-0-130-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:21:47Z"
    - latency: 1.428356ms
      message: 'network-check-target-ip-10-0-130-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:20:47Z"
    - latency: 1.122602ms
      message: 'network-check-target-ip-10-0-130-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:19:47Z"
    - latency: 1.077816ms
      message: 'network-check-target-ip-10-0-130-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:18:47Z"
    - latency: 849.832µs
      message: 'network-check-target-ip-10-0-130-172: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:17:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-172-to-network-check-target-ip-10-0-132-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-172.ec2.internal
      uid: ac90309c-2da7-475b-83be-92bc58cd322a
    resourceVersion: "54544"
    uid: cc0f05f9-3a35-43c0-9594-633d0517acb5
  spec:
    sourcePod: network-check-source-989f8b8dc-79r5t
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:58:47Z"
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.401623ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:47Z"
    - latency: 2.197952ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:47Z"
    - latency: 2.797564ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:47Z"
    - latency: 2.337692ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:47Z"
    - latency: 2.302879ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:22:47Z"
    - latency: 9.261081ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:21:47Z"
    - latency: 2.427954ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:20:47Z"
    - latency: 2.367348ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:19:47Z"
    - latency: 2.172107ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:18:47Z"
    - latency: 2.188432ms
      message: 'network-check-target-ip-10-0-132-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:17:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-172-to-network-check-target-ip-10-0-138-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-172.ec2.internal
      uid: ac90309c-2da7-475b-83be-92bc58cd322a
    resourceVersion: "54543"
    uid: f42d927f-296e-46ff-b142-f0cdc9c87b9c
  spec:
    sourcePod: network-check-source-989f8b8dc-79r5t
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:58:47Z"
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.398934ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:47Z"
    - latency: 2.161145ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:47Z"
    - latency: 2.156717ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:47Z"
    - latency: 2.822412ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:47Z"
    - latency: 2.218809ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:22:47Z"
    - latency: 4.643175ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:21:47Z"
    - latency: 2.063479ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:20:47Z"
    - latency: 2.710668ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:19:47Z"
    - latency: 2.173383ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:18:47Z"
    - latency: 2.144086ms
      message: 'network-check-target-ip-10-0-138-192: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:17:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:51:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-172-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-172.ec2.internal
      uid: ac90309c-2da7-475b-83be-92bc58cd322a
    resourceVersion: "55467"
    uid: e57dd5bd-0de0-4688-a787-262216732f0f
  spec:
    sourcePod: network-check-source-989f8b8dc-79r5t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:57:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 945.467µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:27:47Z"
    - latency: 1.73746ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:27:47Z"
    - latency: 789.461µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:26:47Z"
    - latency: 1.774694ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:26:47Z"
    - latency: 861.712µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:25:47Z"
    - latency: 2.570356ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:25:47Z"
    - latency: 1.400709ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:24:47Z"
    - latency: 2.629554ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:24:47Z"
    - latency: 1.117732ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:23:47Z"
    - latency: 1.770289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:23:47Z"
kind: List
metadata:
  resourceVersion: ""