apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:38:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: dc68e188-2a9d-45a8-8f39-7df42597a3c4
    resourceVersion: "17671"
    uid: 1173cb43-3858-4e64-a7a7-c134677657ed
  spec:
    sourcePod: network-check-source-8894fc9bd-dzhlw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:45:17Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.050538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:52:17Z"
    - latency: 1.044358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:51:17Z"
    - latency: 983.688µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:50:17Z"
    - latency: 1.087362ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:49:17Z"
    - latency: 1.328765ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:48:17Z"
    - latency: 1.380527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:47:17Z"
    - latency: 930.38µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:46:17Z"
    - latency: 952.687µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:45:17Z"
    - latency: 790.361µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:44:17Z"
    - latency: 1.572344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:43:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:38:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: dc68e188-2a9d-45a8-8f39-7df42597a3c4
    resourceVersion: "19795"
    uid: b901b9c8-ab8d-407e-82ce-a0ab80e7f45b
  spec:
    sourcePod: network-check-source-8894fc9bd-dzhlw
    targetEndpoint: a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:44:17Z"
      message: 'load-balancer-api-external: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.817988ms
      message: 'load-balancer-api-external: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:56:17Z"
    - latency: 7.101636ms
      message: 'load-balancer-api-external: resolved host name a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:56:17Z"
    - latency: 3.995513ms
      message: 'load-balancer-api-external: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:55:17Z"
    - latency: 9.304401ms
      message: 'load-balancer-api-external: resolved host name a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:55:17Z"
    - latency: 5.693075ms
      message: 'load-balancer-api-external: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:54:17Z"
    - latency: 6.660821ms
      message: 'load-balancer-api-external: resolved host name a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:54:17Z"
    - latency: 4.795978ms
      message: 'load-balancer-api-external: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:53:17Z"
    - latency: 7.220138ms
      message: 'load-balancer-api-external: resolved host name a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:53:17Z"
    - latency: 5.565383ms
      message: 'load-balancer-api-external: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:52:17Z"
    - latency: 8.089953ms
      message: 'load-balancer-api-external: resolved host name a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:52:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:38:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: dc68e188-2a9d-45a8-8f39-7df42597a3c4
    resourceVersion: "19794"
    uid: f0b39687-8565-481c-a51c-ad4d615fc6e5
  spec:
    sourcePod: network-check-source-8894fc9bd-dzhlw
    targetEndpoint: a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:44:17Z"
      message: 'load-balancer-api-internal: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.196024ms
      message: 'load-balancer-api-internal: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:56:17Z"
    - latency: 7.044752ms
      message: 'load-balancer-api-internal: resolved host name a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:56:17Z"
    - latency: 4.012825ms
      message: 'load-balancer-api-internal: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:55:17Z"
    - latency: 9.165899ms
      message: 'load-balancer-api-internal: resolved host name a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:55:17Z"
    - latency: 5.649928ms
      message: 'load-balancer-api-internal: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:54:17Z"
    - latency: 6.717158ms
      message: 'load-balancer-api-internal: resolved host name a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:54:17Z"
    - latency: 4.796414ms
      message: 'load-balancer-api-internal: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:53:17Z"
    - latency: 7.146183ms
      message: 'load-balancer-api-internal: resolved host name a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:53:17Z"
    - latency: 5.544804ms
      message: 'load-balancer-api-internal: tcp connection to a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:52:17Z"
    - latency: 8.050283ms
      message: 'load-balancer-api-internal: resolved host name a769dad51a4344108b8f25f338576fc2-85ca63c680b8c372.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:52:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:38:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-ip-10-0-133-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: dc68e188-2a9d-45a8-8f39-7df42597a3c4
    resourceVersion: "17669"
    uid: fe500c27-858b-4030-ad1d-e388936eec1b
  spec:
    sourcePod: network-check-source-8894fc9bd-dzhlw
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:45:17Z"
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.19989ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:52:17Z"
    - latency: 2.188873ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:51:17Z"
    - latency: 2.087198ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:50:17Z"
    - latency: 2.229212ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:49:17Z"
    - latency: 2.068366ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:48:17Z"
    - latency: 2.107419ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:47:17Z"
    - latency: 2.076513ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:46:17Z"
    - latency: 2.089663ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:45:17Z"
    - latency: 2.075156ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:44:17Z"
    - latency: 2.416728ms
      message: 'network-check-target-ip-10-0-133-158: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:43:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:38:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-ip-10-0-133-237
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: dc68e188-2a9d-45a8-8f39-7df42597a3c4
    resourceVersion: "17668"
    uid: f640a72b-bcb7-4b02-aa53-5f0c0b40c0ec
  spec:
    sourcePod: network-check-source-8894fc9bd-dzhlw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:45:17Z"
      message: 'network-check-target-ip-10-0-133-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.66829ms
      message: 'network-check-target-ip-10-0-133-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:52:17Z"
    - latency: 1.7116ms
      message: 'network-check-target-ip-10-0-133-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:51:17Z"
    - latency: 1.837951ms
      message: 'network-check-target-ip-10-0-133-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:50:17Z"
    - latency: 1.861742ms
      message: 'network-check-target-ip-10-0-133-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:49:17Z"
    - latency: 1.713223ms
      message: 'network-check-target-ip-10-0-133-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:48:17Z"
    - latency: 1.701972ms
      message: 'network-check-target-ip-10-0-133-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:47:17Z"
    - latency: 1.769915ms
      message: 'network-check-target-ip-10-0-133-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:46:17Z"
    - latency: 1.70944ms
      message: 'network-check-target-ip-10-0-133-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:45:17Z"
    - latency: 1.604564ms
      message: 'network-check-target-ip-10-0-133-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:44:17Z"
    - latency: 2.037249ms
      message: 'network-check-target-ip-10-0-133-237: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:43:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:38:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-ip-10-0-136-162
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: dc68e188-2a9d-45a8-8f39-7df42597a3c4
    resourceVersion: "17670"
    uid: bfdd70c0-e19e-4a82-a71a-c9c2ba6b33ac
  spec:
    sourcePod: network-check-source-8894fc9bd-dzhlw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:45:17Z"
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.218879ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:52:17Z"
    - latency: 881.095µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:51:17Z"
    - latency: 1.499451ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:50:17Z"
    - latency: 1.380549ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:49:17Z"
    - latency: 747.596µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:48:17Z"
    - latency: 1.023725ms
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:47:17Z"
    - latency: 897.992µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:46:17Z"
    - latency: 804.756µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:45:17Z"
    - latency: 779.619µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:44:17Z"
    - latency: 908.4µs
      message: 'network-check-target-ip-10-0-136-162: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:43:17Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-21T15:38:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-162-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-162.ec2.internal
      uid: dc68e188-2a9d-45a8-8f39-7df42597a3c4
    resourceVersion: "19793"
    uid: 47ec91e1-97e3-4365-8cef-6df9ce0cc290
  spec:
    sourcePod: network-check-source-8894fc9bd-dzhlw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-21T15:44:17Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 835.872µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:56:17Z"
    - latency: 1.688987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:56:17Z"
    - latency: 784.722µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:55:17Z"
    - latency: 1.622775ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:55:17Z"
    - latency: 967.985µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:54:17Z"
    - latency: 1.651142ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:54:17Z"
    - latency: 808.562µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:53:17Z"
    - latency: 1.88296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:53:17Z"
    - latency: 746.134µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-21T15:52:17Z"
    - latency: 1.754882ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-21T15:52:17Z"
kind: List
metadata:
  resourceVersion: ""