apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-158-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-158.ec2.internal
      uid: 89c29d3e-9aeb-4122-805b-aebbacc22d20
    resourceVersion: "19376"
    uid: 0c4d66a2-21cc-4a8e-bf91-bb3fe968f9d3
  spec:
    sourcePod: network-check-source-6f8b768455-swmmq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:25:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.255453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:39:45Z"
    - latency: 816.288µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:38:45Z"
    - latency: 1.044891ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:37:45Z"
    - latency: 1.116584ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:36:45Z"
    - latency: 882.752µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:35:45Z"
    - latency: 1.427778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:34:45Z"
    - latency: 912.407µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:33:45Z"
    - latency: 1.066487ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:32:45Z"
    - latency: 1.441373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:31:45Z"
    - latency: 2.167678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:30:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-158-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-158.ec2.internal
      uid: 89c29d3e-9aeb-4122-805b-aebbacc22d20
    resourceVersion: "20590"
    uid: 9d732069-6774-4f3f-b7a3-b9fa406b7c5f
  spec:
    sourcePod: network-check-source-6f8b768455-swmmq
    targetEndpoint: ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:24:45Z"
      message: 'load-balancer-api-external: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.713975ms
      message: 'load-balancer-api-external: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:42:45Z"
    - latency: 7.848699ms
      message: 'load-balancer-api-external: resolved host name ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:42:45Z"
    - latency: 4.46923ms
      message: 'load-balancer-api-external: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:41:45Z"
    - latency: 7.177167ms
      message: 'load-balancer-api-external: resolved host name ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:41:45Z"
    - latency: 4.762127ms
      message: 'load-balancer-api-external: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:40:45Z"
    - latency: 8.295388ms
      message: 'load-balancer-api-external: resolved host name ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:40:45Z"
    - latency: 4.529067ms
      message: 'load-balancer-api-external: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:39:45Z"
    - latency: 7.654898ms
      message: 'load-balancer-api-external: resolved host name ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:39:45Z"
    - latency: 4.712615ms
      message: 'load-balancer-api-external: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:38:45Z"
    - latency: 7.503ms
      message: 'load-balancer-api-external: resolved host name ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:38:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-158-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-158.ec2.internal
      uid: 89c29d3e-9aeb-4122-805b-aebbacc22d20
    resourceVersion: "20591"
    uid: 7efb9090-a184-4f89-b671-108addad79bd
  spec:
    sourcePod: network-check-source-6f8b768455-swmmq
    targetEndpoint: ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:24:45Z"
      message: 'load-balancer-api-internal: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.677697ms
      message: 'load-balancer-api-internal: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:42:45Z"
    - latency: 7.789934ms
      message: 'load-balancer-api-internal: resolved host name ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:42:45Z"
    - latency: 4.655946ms
      message: 'load-balancer-api-internal: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:41:45Z"
    - latency: 7.199661ms
      message: 'load-balancer-api-internal: resolved host name ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:41:45Z"
    - latency: 5.299007ms
      message: 'load-balancer-api-internal: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:40:45Z"
    - latency: 8.208336ms
      message: 'load-balancer-api-internal: resolved host name ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:40:45Z"
    - latency: 4.51728ms
      message: 'load-balancer-api-internal: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:39:45Z"
    - latency: 7.688619ms
      message: 'load-balancer-api-internal: resolved host name ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:39:45Z"
    - latency: 4.763614ms
      message: 'load-balancer-api-internal: tcp connection to ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:38:45Z"
    - latency: 7.460783ms
      message: 'load-balancer-api-internal: resolved host name ab3d2b56abfc44a3a93963896ddfa467-8e7ebcf1e278ddf1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:38:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-158-to-network-check-target-ip-10-0-132-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-158.ec2.internal
      uid: 89c29d3e-9aeb-4122-805b-aebbacc22d20
    resourceVersion: "19375"
    uid: 059b1861-436e-4054-a305-081b2a72de08
  spec:
    sourcePod: network-check-source-6f8b768455-swmmq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:25:45Z"
      message: 'network-check-target-ip-10-0-132-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.504696ms
      message: 'network-check-target-ip-10-0-132-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:39:45Z"
    - latency: 1.0016ms
      message: 'network-check-target-ip-10-0-132-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:38:45Z"
    - latency: 1.006739ms
      message: 'network-check-target-ip-10-0-132-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:37:45Z"
    - latency: 1.471131ms
      message: 'network-check-target-ip-10-0-132-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:36:45Z"
    - latency: 909.535µs
      message: 'network-check-target-ip-10-0-132-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:35:45Z"
    - latency: 927.528µs
      message: 'network-check-target-ip-10-0-132-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:34:45Z"
    - latency: 1.506467ms
      message: 'network-check-target-ip-10-0-132-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:33:45Z"
    - latency: 1.1648ms
      message: 'network-check-target-ip-10-0-132-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:32:45Z"
    - latency: 1.302877ms
      message: 'network-check-target-ip-10-0-132-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:31:45Z"
    - latency: 913.783µs
      message: 'network-check-target-ip-10-0-132-158: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:30:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-158-to-network-check-target-ip-10-0-136-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-158.ec2.internal
      uid: 89c29d3e-9aeb-4122-805b-aebbacc22d20
    resourceVersion: "19373"
    uid: e2ed5f1e-3bd4-4c07-8e1d-f8322afc023e
  spec:
    sourcePod: network-check-source-6f8b768455-swmmq
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:25:45Z"
      message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.910713ms
      message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:39:45Z"
    - latency: 1.885455ms
      message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:38:45Z"
    - latency: 1.820964ms
      message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:37:45Z"
    - latency: 2.002914ms
      message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:36:45Z"
    - latency: 2.554565ms
      message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:35:45Z"
    - latency: 1.946892ms
      message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:34:45Z"
    - latency: 1.867262ms
      message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:33:45Z"
    - latency: 1.916264ms
      message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:32:45Z"
    - latency: 2.36091ms
      message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:31:45Z"
    - latency: 2.261676ms
      message: 'network-check-target-ip-10-0-136-33: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:30:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-158-to-network-check-target-ip-10-0-142-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-158.ec2.internal
      uid: 89c29d3e-9aeb-4122-805b-aebbacc22d20
    resourceVersion: "19374"
    uid: a9c8e28c-6f74-410d-919a-23bf11c2ca77
  spec:
    sourcePod: network-check-source-6f8b768455-swmmq
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:25:45Z"
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.146946ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:39:45Z"
    - latency: 2.065936ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:38:45Z"
    - latency: 2.44008ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:37:45Z"
    - latency: 2.214169ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:36:45Z"
    - latency: 1.946519ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:35:45Z"
    - latency: 2.439919ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:34:45Z"
    - latency: 2.100307ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:33:45Z"
    - latency: 2.12068ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:32:45Z"
    - latency: 2.371797ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:31:45Z"
    - latency: 2.627651ms
      message: 'network-check-target-ip-10-0-142-220: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:30:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T09:18:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-158-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-158.ec2.internal
      uid: 89c29d3e-9aeb-4122-805b-aebbacc22d20
    resourceVersion: "20589"
    uid: 73e5bcf3-845a-4a71-998b-66210d4928ec
  spec:
    sourcePod: network-check-source-6f8b768455-swmmq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T09:24:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.829µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:42:45Z"
    - latency: 1.796985ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:42:45Z"
    - latency: 1.22709ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:41:45Z"
    - latency: 1.641361ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:41:45Z"
    - latency: 886.609µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:40:45Z"
    - latency: 2.268339ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:40:45Z"
    - latency: 972.866µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:39:45Z"
    - latency: 2.206596ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:39:45Z"
    - latency: 876.878µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T09:38:45Z"
    - latency: 1.845421ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T09:38:45Z"
kind: List
metadata:
  resourceVersion: ""