apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:09:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-73-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-73.ec2.internal
      uid: ef93552d-aa5d-4f45-97f1-4ee9c89173e4
    resourceVersion: "26696"
    uid: ef53dd53-5d89-41d0-bd54-895fe20a0956
  spec:
    sourcePod: network-check-source-6f78d59f99-5hg9b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:16:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 910.77µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:42Z"
    - latency: 1.215101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:42Z"
    - latency: 3.976807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:42Z"
    - latency: 1.171682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:42Z"
    - latency: 1.571279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:42Z"
    - latency: 1.073473ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:42Z"
    - latency: 1.013059ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:42Z"
    - latency: 1.159294ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:42Z"
    - latency: 855.638µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:42Z"
    - latency: 1.107411ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:09:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-73-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-73.ec2.internal
      uid: ef93552d-aa5d-4f45-97f1-4ee9c89173e4
    resourceVersion: "26298"
    uid: efd1a14f-9600-4064-9de2-895127f590d8
  spec:
    sourcePod: network-check-source-6f78d59f99-5hg9b
    targetEndpoint: ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:15:42Z"
      message: 'load-balancer-api-external: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.56996ms
      message: 'load-balancer-api-external: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:42Z"
    - latency: 6.649625ms
      message: 'load-balancer-api-external: resolved host name ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:57:42Z"
    - latency: 17.676372ms
      message: 'load-balancer-api-external: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:42Z"
    - latency: 10.782447ms
      message: 'load-balancer-api-external: resolved host name ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:42Z"
    - latency: 17.956848ms
      message: 'load-balancer-api-external: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:42Z"
    - latency: 7.478824ms
      message: 'load-balancer-api-external: resolved host name ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:55:42Z"
    - latency: 19.000239ms
      message: 'load-balancer-api-external: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:42Z"
    - latency: 6.826248ms
      message: 'load-balancer-api-external: resolved host name ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:54:42Z"
    - latency: 20.25214ms
      message: 'load-balancer-api-external: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:42Z"
    - latency: 7.062057ms
      message: 'load-balancer-api-external: resolved host name ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:53:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:09:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-73-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-73.ec2.internal
      uid: ef93552d-aa5d-4f45-97f1-4ee9c89173e4
    resourceVersion: "26297"
    uid: 07d1cd41-394a-4549-9d65-b59c79b316c0
  spec:
    sourcePod: network-check-source-6f78d59f99-5hg9b
    targetEndpoint: ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:15:42Z"
      message: 'load-balancer-api-internal: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.811381ms
      message: 'load-balancer-api-internal: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:42Z"
    - latency: 6.574649ms
      message: 'load-balancer-api-internal: resolved host name ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:57:42Z"
    - latency: 19.169659ms
      message: 'load-balancer-api-internal: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:42Z"
    - latency: 10.86944ms
      message: 'load-balancer-api-internal: resolved host name ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:42Z"
    - latency: 18.006642ms
      message: 'load-balancer-api-internal: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:42Z"
    - latency: 7.406606ms
      message: 'load-balancer-api-internal: resolved host name ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:55:42Z"
    - latency: 19.001078ms
      message: 'load-balancer-api-internal: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:42Z"
    - latency: 6.918127ms
      message: 'load-balancer-api-internal: resolved host name ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:54:42Z"
    - latency: 19.894508ms
      message: 'load-balancer-api-internal: tcp connection to ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:42Z"
    - latency: 6.983992ms
      message: 'load-balancer-api-internal: resolved host name ac99b34dec53a4e5591169d0150bfba6-6dfbb869b57b1e02.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:53:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:09:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-73-to-network-check-target-ip-10-0-130-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-73.ec2.internal
      uid: ef93552d-aa5d-4f45-97f1-4ee9c89173e4
    resourceVersion: "26695"
    uid: d075fd16-a435-4771-90e5-a6b0c8b9e19f
  spec:
    sourcePod: network-check-source-6f78d59f99-5hg9b
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:16:42Z"
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.972226ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:42Z"
    - latency: 1.845167ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:42Z"
    - latency: 2.272957ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:42Z"
    - latency: 2.05747ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:42Z"
    - latency: 2.09079ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:42Z"
    - latency: 1.898797ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:42Z"
    - latency: 2.017723ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:42Z"
    - latency: 1.951206ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:42Z"
    - latency: 1.984876ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:42Z"
    - latency: 2.013952ms
      message: 'network-check-target-ip-10-0-130-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:09:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-73-to-network-check-target-ip-10-0-131-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-73.ec2.internal
      uid: ef93552d-aa5d-4f45-97f1-4ee9c89173e4
    resourceVersion: "26694"
    uid: ecc52309-3a1f-428c-8f3d-818c74a0241c
  spec:
    sourcePod: network-check-source-6f78d59f99-5hg9b
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:16:42Z"
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.944004ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:42Z"
    - latency: 2.27642ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:42Z"
    - latency: 2.28469ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:42Z"
    - latency: 2.258825ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:42Z"
    - latency: 2.260443ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:42Z"
    - latency: 2.044128ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:42Z"
    - latency: 2.469849ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:42Z"
    - latency: 2.337897ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:42Z"
    - latency: 2.02229ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:42Z"
    - latency: 2.271456ms
      message: 'network-check-target-ip-10-0-131-94: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:09:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-73-to-network-check-target-ip-10-0-139-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-73.ec2.internal
      uid: ef93552d-aa5d-4f45-97f1-4ee9c89173e4
    resourceVersion: "26693"
    uid: 42c41810-94aa-4d35-b5c4-94f9c25d7cb4
  spec:
    sourcePod: network-check-source-6f78d59f99-5hg9b
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:16:42Z"
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.06µs
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:58:42Z"
    - latency: 1.016335ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:42Z"
    - latency: 1.866156ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:42Z"
    - latency: 1.672976ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:42Z"
    - latency: 1.521777ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:42Z"
    - latency: 1.462744ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:42Z"
    - latency: 882.378µs
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:52:42Z"
    - latency: 1.581676ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:51:42Z"
    - latency: 906.78µs
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:50:42Z"
    - latency: 1.308808ms
      message: 'network-check-target-ip-10-0-139-73: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:49:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T22:09:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-73-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-73.ec2.internal
      uid: ef93552d-aa5d-4f45-97f1-4ee9c89173e4
    resourceVersion: "26296"
    uid: 879d5041-39c7-4207-929a-cf8050a80fe9
  spec:
    sourcePod: network-check-source-6f78d59f99-5hg9b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T22:15:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 950.149µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:57:42Z"
    - latency: 1.634271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:57:42Z"
    - latency: 1.536298ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:56:42Z"
    - latency: 3.204992ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:56:42Z"
    - latency: 931.105µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:55:42Z"
    - latency: 1.587095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:55:42Z"
    - latency: 1.031175ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:54:42Z"
    - latency: 1.814422ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:54:42Z"
    - latency: 1.246229ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T22:53:42Z"
    - latency: 1.826766ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T22:53:42Z"
kind: List
metadata:
  resourceVersion: ""