apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-163-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-163.ec2.internal
      uid: 38fef7b7-d642-49af-88d9-fb7460b7e2df
    resourceVersion: "77871"
    uid: 8d32efcb-811b-425f-9fda-2ad15ceed7c3
  spec:
    sourcePod: network-check-source-65bdbbff45-4l8h2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T18:54:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.191563ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:43:02Z"
    - latency: 969.401µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:42:02Z"
    - latency: 1.065263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:41:02Z"
    - latency: 1.358986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:40:02Z"
    - latency: 1.294701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:39:02Z"
    - latency: 1.208264ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:38:02Z"
    - latency: 1.016505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:37:02Z"
    - latency: 1.136861ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:36:02Z"
    - latency: 916.296µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:35:02Z"
    - latency: 1.059637ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-163-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-163.ec2.internal
      uid: 38fef7b7-d642-49af-88d9-fb7460b7e2df
    resourceVersion: "75746"
    uid: f53e794f-1398-497b-b6aa-1d34d503ece0
  spec:
    sourcePod: network-check-source-65bdbbff45-4l8h2
    targetEndpoint: ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T18:53:02Z"
      message: 'load-balancer-api-external: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.370377ms
      message: 'load-balancer-api-external: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:41:02Z"
    - latency: 7.049851ms
      message: 'load-balancer-api-external: resolved host name ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:41:02Z"
    - latency: 4.405766ms
      message: 'load-balancer-api-external: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:40:02Z"
    - latency: 10.128253ms
      message: 'load-balancer-api-external: resolved host name ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:40:02Z"
    - latency: 4.727067ms
      message: 'load-balancer-api-external: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:39:02Z"
    - latency: 9.48492ms
      message: 'load-balancer-api-external: resolved host name ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:39:02Z"
    - latency: 4.228839ms
      message: 'load-balancer-api-external: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:38:02Z"
    - latency: 9.792655ms
      message: 'load-balancer-api-external: resolved host name ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:38:02Z"
    - latency: 4.567475ms
      message: 'load-balancer-api-external: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:37:02Z"
    - latency: 9.390117ms
      message: 'load-balancer-api-external: resolved host name ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:37:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-163-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-163.ec2.internal
      uid: 38fef7b7-d642-49af-88d9-fb7460b7e2df
    resourceVersion: "75745"
    uid: 457886fc-7242-4a0d-a86f-de848d730a57
  spec:
    sourcePod: network-check-source-65bdbbff45-4l8h2
    targetEndpoint: ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T18:53:02Z"
      message: 'load-balancer-api-internal: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.362202ms
      message: 'load-balancer-api-internal: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:41:02Z"
    - latency: 7.180778ms
      message: 'load-balancer-api-internal: resolved host name ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:41:02Z"
    - latency: 4.617408ms
      message: 'load-balancer-api-internal: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:40:02Z"
    - latency: 10.228741ms
      message: 'load-balancer-api-internal: resolved host name ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:40:02Z"
    - latency: 4.403429ms
      message: 'load-balancer-api-internal: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:39:02Z"
    - latency: 9.567329ms
      message: 'load-balancer-api-internal: resolved host name ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:39:02Z"
    - latency: 4.556174ms
      message: 'load-balancer-api-internal: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:38:02Z"
    - latency: 9.852533ms
      message: 'load-balancer-api-internal: resolved host name ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:38:02Z"
    - latency: 4.919558ms
      message: 'load-balancer-api-internal: tcp connection to ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:37:02Z"
    - latency: 9.500687ms
      message: 'load-balancer-api-internal: resolved host name ad4dc93446e6d460d8a720fc137f0f99-0fbbe89d6ed6d16d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:37:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-163-to-network-check-target-ip-10-0-128-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-163.ec2.internal
      uid: 38fef7b7-d642-49af-88d9-fb7460b7e2df
    resourceVersion: "77867"
    uid: b642bddc-f390-477a-9f06-4cdc023d011d
  spec:
    sourcePod: network-check-source-65bdbbff45-4l8h2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T18:54:02Z"
      message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 819.482µs
      message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:43:02Z"
    - latency: 1.598841ms
      message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:42:02Z"
    - latency: 1.857191ms
      message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:41:02Z"
    - latency: 1.034953ms
      message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:40:02Z"
    - latency: 1.071263ms
      message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:39:02Z"
    - latency: 805.596µs
      message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:38:02Z"
    - latency: 911.878µs
      message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:37:02Z"
    - latency: 974.076µs
      message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:36:02Z"
    - latency: 984.812µs
      message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:35:02Z"
    - latency: 1.019723ms
      message: 'network-check-target-ip-10-0-128-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-163-to-network-check-target-ip-10-0-139-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-163.ec2.internal
      uid: 38fef7b7-d642-49af-88d9-fb7460b7e2df
    resourceVersion: "77870"
    uid: 6606cebd-2bd4-4662-b800-f343f7842816
  spec:
    sourcePod: network-check-source-65bdbbff45-4l8h2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T18:54:02Z"
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.234506ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:43:02Z"
    - latency: 2.098964ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:42:02Z"
    - latency: 2.376246ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:41:02Z"
    - latency: 2.060345ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:40:02Z"
    - latency: 2.365715ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:39:02Z"
    - latency: 2.270624ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:38:02Z"
    - latency: 2.049959ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:37:02Z"
    - latency: 2.106805ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:36:02Z"
    - latency: 2.020407ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:35:02Z"
    - latency: 2.056709ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-163-to-network-check-target-ip-10-0-139-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-163.ec2.internal
      uid: 38fef7b7-d642-49af-88d9-fb7460b7e2df
    resourceVersion: "77869"
    uid: 826027e2-184f-474b-a7ab-e45a8ea8bde9
  spec:
    sourcePod: network-check-source-65bdbbff45-4l8h2
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T18:54:02Z"
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.005114ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:43:02Z"
    - latency: 2.411522ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:42:02Z"
    - latency: 2.840528ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:41:02Z"
    - latency: 2.424846ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:40:02Z"
    - latency: 2.405868ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:39:02Z"
    - latency: 2.318486ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:38:02Z"
    - latency: 2.165182ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:37:02Z"
    - latency: 2.54328ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:36:02Z"
    - latency: 2.204863ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:35:02Z"
    - latency: 2.543805ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-31T18:47:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-163-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-163.ec2.internal
      uid: 38fef7b7-d642-49af-88d9-fb7460b7e2df
    resourceVersion: "75744"
    uid: 5be78990-4cbc-44bd-95dc-2bf16d660c52
  spec:
    sourcePod: network-check-source-65bdbbff45-4l8h2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-31T18:53:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 942.642µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:41:02Z"
    - latency: 2.254733ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:41:02Z"
    - latency: 1.049118ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:40:02Z"
    - latency: 2.11425ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:40:02Z"
    - latency: 1.404743ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:39:02Z"
    - latency: 1.897686ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:39:02Z"
    - latency: 1.311963ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:38:02Z"
    - latency: 1.808507ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:38:02Z"
    - latency: 962.981µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-31T19:37:02Z"
    - latency: 1.892956ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-31T19:37:02Z"
kind: List
metadata:
  resourceVersion: ""