apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:51:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: 66072a33-c5df-4bcc-b502-614f7f568e8d
    resourceVersion: "66071"
    uid: 8ca1ab93-abe0-440f-94b9-32aadbd63f7f
  spec:
    sourcePod: network-check-source-6f8b768455-jxzxx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:58:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 998.058µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:19Z"
    - latency: 1.552197ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:19Z"
    - latency: 1.331009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:19Z"
    - latency: 1.159909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:23:19Z"
    - latency: 1.317223ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:22:19Z"
    - latency: 1.111587ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:21:19Z"
    - latency: 946.845µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:20:19Z"
    - latency: 962.967µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:19:19Z"
    - latency: 769.535µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:18:19Z"
    - latency: 4.285969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:17:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:51:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: 66072a33-c5df-4bcc-b502-614f7f568e8d
    resourceVersion: "67015"
    uid: daec4437-0666-455e-857a-c1cff3f0b29d
  spec:
    sourcePod: network-check-source-6f8b768455-jxzxx
    targetEndpoint: a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:57:19Z"
      message: 'load-balancer-api-external: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.773855ms
      message: 'load-balancer-api-external: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:27:19Z"
    - latency: 8.077458ms
      message: 'load-balancer-api-external: resolved host name a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:27:19Z"
    - latency: 4.162345ms
      message: 'load-balancer-api-external: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:19Z"
    - latency: 8.511357ms
      message: 'load-balancer-api-external: resolved host name a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:26:19Z"
    - latency: 3.80106ms
      message: 'load-balancer-api-external: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:19Z"
    - latency: 9.058723ms
      message: 'load-balancer-api-external: resolved host name a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:25:19Z"
    - latency: 5.072304ms
      message: 'load-balancer-api-external: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:19Z"
    - latency: 8.819534ms
      message: 'load-balancer-api-external: resolved host name a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:24:19Z"
    - latency: 4.205719ms
      message: 'load-balancer-api-external: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:23:19Z"
    - latency: 8.373062ms
      message: 'load-balancer-api-external: resolved host name a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:23:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:51:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: 66072a33-c5df-4bcc-b502-614f7f568e8d
    resourceVersion: "67016"
    uid: b87bf8ea-354b-465d-8c40-6d834e3ffcf3
  spec:
    sourcePod: network-check-source-6f8b768455-jxzxx
    targetEndpoint: a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:57:19Z"
      message: 'load-balancer-api-internal: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.797153ms
      message: 'load-balancer-api-internal: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:27:19Z"
    - latency: 8.189292ms
      message: 'load-balancer-api-internal: resolved host name a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:27:19Z"
    - latency: 4.089952ms
      message: 'load-balancer-api-internal: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:19Z"
    - latency: 8.551742ms
      message: 'load-balancer-api-internal: resolved host name a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:26:19Z"
    - latency: 3.175928ms
      message: 'load-balancer-api-internal: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:19Z"
    - latency: 9.018538ms
      message: 'load-balancer-api-internal: resolved host name a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:25:19Z"
    - latency: 4.444378ms
      message: 'load-balancer-api-internal: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:19Z"
    - latency: 8.876067ms
      message: 'load-balancer-api-internal: resolved host name a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:24:19Z"
    - latency: 4.240541ms
      message: 'load-balancer-api-internal: tcp connection to a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:23:19Z"
    - latency: 8.251962ms
      message: 'load-balancer-api-internal: resolved host name a079ba4afc4ec4ffcb5f26c39421e355-bacaf3b8e223c4d6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:23:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:51:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-network-check-target-ip-10-0-128-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: 66072a33-c5df-4bcc-b502-614f7f568e8d
    resourceVersion: "66068"
    uid: 04bf1684-eeab-456e-9dc4-aeb0d15aebbb
  spec:
    sourcePod: network-check-source-6f8b768455-jxzxx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:58:19Z"
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.042327ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:19Z"
    - latency: 1.518273ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:19Z"
    - latency: 1.275899ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:19Z"
    - latency: 967.002µs
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:23:19Z"
    - latency: 836.851µs
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:22:19Z"
    - latency: 1.797423ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:21:19Z"
    - latency: 994.272µs
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:20:19Z"
    - latency: 858.879µs
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:19:19Z"
    - latency: 1.122649ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:18:19Z"
    - latency: 5.416307ms
      message: 'network-check-target-ip-10-0-128-30: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:17:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:51:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-network-check-target-ip-10-0-138-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: 66072a33-c5df-4bcc-b502-614f7f568e8d
    resourceVersion: "66070"
    uid: 6eb59b2b-99e7-47c9-b549-9bac6d8b0fb5
  spec:
    sourcePod: network-check-source-6f8b768455-jxzxx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:58:19Z"
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.964081ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:19Z"
    - latency: 2.026461ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:19Z"
    - latency: 1.942985ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:19Z"
    - latency: 1.882189ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:23:19Z"
    - latency: 1.881948ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:22:19Z"
    - latency: 2.020467ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:21:19Z"
    - latency: 2.101082ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:20:19Z"
    - latency: 1.629489ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:19:19Z"
    - latency: 2.314913ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:18:19Z"
    - latency: 4.316433ms
      message: 'network-check-target-ip-10-0-138-28: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:17:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:51:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-network-check-target-ip-10-0-143-250
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: 66072a33-c5df-4bcc-b502-614f7f568e8d
    resourceVersion: "66069"
    uid: ee479215-0170-41aa-8531-0a1aa7dcf12a
  spec:
    sourcePod: network-check-source-6f8b768455-jxzxx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:58:19Z"
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.209684ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:19Z"
    - latency: 2.393476ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:19Z"
    - latency: 2.539114ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:19Z"
    - latency: 2.34725ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:23:19Z"
    - latency: 2.205914ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:22:19Z"
    - latency: 2.578069ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:21:19Z"
    - latency: 2.074949ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:20:19Z"
    - latency: 2.754051ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:19:19Z"
    - latency: 2.295645ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:18:19Z"
    - latency: 4.835067ms
      message: 'network-check-target-ip-10-0-143-250: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:17:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T07:51:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-30-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-30.ec2.internal
      uid: 66072a33-c5df-4bcc-b502-614f7f568e8d
    resourceVersion: "67014"
    uid: 3ea5b371-17ed-421f-b565-8da58b9ae5a0
  spec:
    sourcePod: network-check-source-6f8b768455-jxzxx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T07:57:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 897.698µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:27:19Z"
    - latency: 1.826855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:27:19Z"
    - latency: 883.291µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:26:19Z"
    - latency: 1.615817ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:26:19Z"
    - latency: 813.598µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:25:19Z"
    - latency: 2.24601ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:25:19Z"
    - latency: 808.876µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:24:19Z"
    - latency: 1.925216ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:24:19Z"
    - latency: 867.095µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T08:23:19Z"
    - latency: 1.876581ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T08:23:19Z"
kind: List
metadata:
  resourceVersion: ""