apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:30:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 5531d98d-653e-40d3-813b-1fad2cb61164
    resourceVersion: "19104"
    uid: 5cb919eb-f85f-49ef-b224-7972750cd0af
  spec:
    sourcePod: network-check-source-8894fc9bd-7dqjb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:37:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.318187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:44:20Z"
    - latency: 795.974µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:43:20Z"
    - latency: 882.016µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:42:20Z"
    - latency: 1.250133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:41:20Z"
    - latency: 862.261µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:40:20Z"
    - latency: 1.127666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:39:20Z"
    - latency: 1.123766ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:38:20Z"
    - latency: 1.552255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:37:20Z"
    - latency: 1.350281ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:36:20Z"
    - latency: 1.207646ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:35:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:30:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 5531d98d-653e-40d3-813b-1fad2cb61164
    resourceVersion: "21204"
    uid: 846b3868-6af6-4bf1-8ee3-7612b8c1c0dd
  spec:
    sourcePod: network-check-source-8894fc9bd-7dqjb
    targetEndpoint: afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:36:20Z"
      message: 'load-balancer-api-external: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.527144ms
      message: 'load-balancer-api-external: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:48:20Z"
    - latency: 8.516177ms
      message: 'load-balancer-api-external: resolved host name afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:48:20Z"
    - latency: 4.467789ms
      message: 'load-balancer-api-external: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:47:20Z"
    - latency: 7.058185ms
      message: 'load-balancer-api-external: resolved host name afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:47:20Z"
    - latency: 4.15658ms
      message: 'load-balancer-api-external: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:46:20Z"
    - latency: 8.488476ms
      message: 'load-balancer-api-external: resolved host name afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:46:20Z"
    - latency: 4.586976ms
      message: 'load-balancer-api-external: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:45:20Z"
    - latency: 6.859689ms
      message: 'load-balancer-api-external: resolved host name afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:45:20Z"
    - latency: 4.897803ms
      message: 'load-balancer-api-external: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:44:20Z"
    - latency: 11.962675ms
      message: 'load-balancer-api-external: resolved host name afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:44:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:30:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 5531d98d-653e-40d3-813b-1fad2cb61164
    resourceVersion: "21203"
    uid: 71203b93-b1a6-4d29-83aa-d38e49fc2634
  spec:
    sourcePod: network-check-source-8894fc9bd-7dqjb
    targetEndpoint: afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:36:20Z"
      message: 'load-balancer-api-internal: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.84581ms
      message: 'load-balancer-api-internal: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:48:20Z"
    - latency: 8.453737ms
      message: 'load-balancer-api-internal: resolved host name afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:48:20Z"
    - latency: 4.372183ms
      message: 'load-balancer-api-internal: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:47:20Z"
    - latency: 7.1175ms
      message: 'load-balancer-api-internal: resolved host name afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:47:20Z"
    - latency: 4.133132ms
      message: 'load-balancer-api-internal: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:46:20Z"
    - latency: 8.535689ms
      message: 'load-balancer-api-internal: resolved host name afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:46:20Z"
    - latency: 4.618857ms
      message: 'load-balancer-api-internal: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:45:20Z"
    - latency: 6.802211ms
      message: 'load-balancer-api-internal: resolved host name afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:45:20Z"
    - latency: 5.020677ms
      message: 'load-balancer-api-internal: tcp connection to afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:44:20Z"
    - latency: 12.130856ms
      message: 'load-balancer-api-internal: resolved host name afc47e3f2927c465b829d3892d897a13-8d20063cf020918a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:44:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:30:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-network-check-target-ip-10-0-134-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 5531d98d-653e-40d3-813b-1fad2cb61164
    resourceVersion: "19102"
    uid: 1cb75903-cc7a-4cb1-82b3-f763634e4388
  spec:
    sourcePod: network-check-source-8894fc9bd-7dqjb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:37:20Z"
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.91227ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:44:20Z"
    - latency: 1.660305ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:43:20Z"
    - latency: 1.727283ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:42:20Z"
    - latency: 1.768571ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:41:20Z"
    - latency: 1.720171ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:40:20Z"
    - latency: 1.66363ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:39:20Z"
    - latency: 1.856482ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:38:20Z"
    - latency: 1.720847ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:37:20Z"
    - latency: 1.836359ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:36:20Z"
    - latency: 1.976469ms
      message: 'network-check-target-ip-10-0-134-82: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:35:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:30:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-network-check-target-ip-10-0-137-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 5531d98d-653e-40d3-813b-1fad2cb61164
    resourceVersion: "19101"
    uid: 139b1e37-eeac-4be5-a444-5ca485878aef
  spec:
    sourcePod: network-check-source-8894fc9bd-7dqjb
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:37:20Z"
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.02128ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:44:20Z"
    - latency: 747.442µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:43:20Z"
    - latency: 872.538µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:42:20Z"
    - latency: 978.614µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:41:20Z"
    - latency: 758.184µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:40:20Z"
    - latency: 1.41195ms
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:39:20Z"
    - latency: 747.618µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:38:20Z"
    - latency: 687.21µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:37:20Z"
    - latency: 872.44µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:36:20Z"
    - latency: 783.033µs
      message: 'network-check-target-ip-10-0-137-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:35:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:30:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-network-check-target-ip-10-0-143-92
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 5531d98d-653e-40d3-813b-1fad2cb61164
    resourceVersion: "19103"
    uid: d98cb8d2-e734-4785-b4aa-f174bf91c68c
  spec:
    sourcePod: network-check-source-8894fc9bd-7dqjb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:37:20Z"
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.779384ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:44:20Z"
    - latency: 1.975983ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:43:20Z"
    - latency: 2.098921ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:42:20Z"
    - latency: 2.450227ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:41:20Z"
    - latency: 1.750127ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:40:20Z"
    - latency: 2.079018ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:39:20Z"
    - latency: 2.15174ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:38:20Z"
    - latency: 1.948544ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:37:20Z"
    - latency: 2.159848ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:36:20Z"
    - latency: 2.167479ms
      message: 'network-check-target-ip-10-0-143-92: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:35:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-24T14:30:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-95-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-95.ec2.internal
      uid: 5531d98d-653e-40d3-813b-1fad2cb61164
    resourceVersion: "21202"
    uid: 6a4dd527-ee74-45e3-ad37-6e865d957e43
  spec:
    sourcePod: network-check-source-8894fc9bd-7dqjb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-24T14:36:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 849.855µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:48:20Z"
    - latency: 1.591138ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:48:20Z"
    - latency: 824.219µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:47:20Z"
    - latency: 1.682514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:47:20Z"
    - latency: 774.811µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:46:20Z"
    - latency: 1.680348ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:46:20Z"
    - latency: 877.571µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:45:20Z"
    - latency: 1.767915ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:45:20Z"
    - latency: 907.48µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-24T14:44:20Z"
    - latency: 1.978367ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-24T14:44:20Z"
kind: List
metadata:
  resourceVersion: ""