apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-85-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-85.ec2.internal
      uid: 001aac4a-8052-4adc-8cf9-84da38a07aeb
    resourceVersion: "39256"
    uid: 1bcc72a4-ed8e-47b5-8500-e46a05772b7c
  spec:
    sourcePod: network-check-source-6f8b768455-25zwg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:36:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.693549ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:18:50Z"
    - latency: 1.281651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:17:50Z"
    - latency: 1.317473ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:16:50Z"
    - latency: 1.248846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:15:50Z"
    - latency: 1.143726ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:14:50Z"
    - latency: 1.036794ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:50Z"
    - latency: 999.84µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:12:50Z"
    - latency: 1.235601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:11:50Z"
    - latency: 1.168932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:10:50Z"
    - latency: 1.712497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:09:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-85-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-85.ec2.internal
      uid: 001aac4a-8052-4adc-8cf9-84da38a07aeb
    resourceVersion: "38822"
    uid: 6cddc662-00f4-4048-9b56-6d00e58868a5
  spec:
    sourcePod: network-check-source-6f8b768455-25zwg
    targetEndpoint: a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:35:50Z"
      message: 'load-balancer-api-external: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.933073ms
      message: 'load-balancer-api-external: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:17:50Z"
    - latency: 7.686238ms
      message: 'load-balancer-api-external: resolved host name a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:17:50Z"
    - latency: 4.104371ms
      message: 'load-balancer-api-external: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:16:50Z"
    - latency: 7.613229ms
      message: 'load-balancer-api-external: resolved host name a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:16:50Z"
    - latency: 5.288235ms
      message: 'load-balancer-api-external: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:15:50Z"
    - latency: 7.626125ms
      message: 'load-balancer-api-external: resolved host name a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:15:50Z"
    - latency: 5.175147ms
      message: 'load-balancer-api-external: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:14:50Z"
    - latency: 8.407776ms
      message: 'load-balancer-api-external: resolved host name a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:14:50Z"
    - latency: 4.578674ms
      message: 'load-balancer-api-external: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:50Z"
    - latency: 7.352017ms
      message: 'load-balancer-api-external: resolved host name a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:13:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-85-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-85.ec2.internal
      uid: 001aac4a-8052-4adc-8cf9-84da38a07aeb
    resourceVersion: "38823"
    uid: 2499e3d6-0c1f-4e81-946b-2742fd5ed407
  spec:
    sourcePod: network-check-source-6f8b768455-25zwg
    targetEndpoint: a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:35:50Z"
      message: 'load-balancer-api-internal: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.879367ms
      message: 'load-balancer-api-internal: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:17:50Z"
    - latency: 7.643833ms
      message: 'load-balancer-api-internal: resolved host name a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:17:50Z"
    - latency: 4.129582ms
      message: 'load-balancer-api-internal: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:16:50Z"
    - latency: 7.652604ms
      message: 'load-balancer-api-internal: resolved host name a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:16:50Z"
    - latency: 5.251582ms
      message: 'load-balancer-api-internal: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:15:50Z"
    - latency: 7.793752ms
      message: 'load-balancer-api-internal: resolved host name a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:15:50Z"
    - latency: 5.133212ms
      message: 'load-balancer-api-internal: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:14:50Z"
    - latency: 8.439824ms
      message: 'load-balancer-api-internal: resolved host name a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:14:50Z"
    - latency: 4.161567ms
      message: 'load-balancer-api-internal: tcp connection to a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:50Z"
    - latency: 7.320145ms
      message: 'load-balancer-api-internal: resolved host name a25c0a3b9c405437081886c582e65d60-a86367109cf49c6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:13:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-85-to-network-check-target-ip-10-0-130-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-85.ec2.internal
      uid: 001aac4a-8052-4adc-8cf9-84da38a07aeb
    resourceVersion: "39255"
    uid: ae058cee-246d-42a2-a392-d89c0567adcf
  spec:
    sourcePod: network-check-source-6f8b768455-25zwg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:36:50Z"
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.384811ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:18:50Z"
    - latency: 2.150456ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:17:50Z"
    - latency: 2.350286ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:16:50Z"
    - latency: 2.250482ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:15:50Z"
    - latency: 2.198911ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:14:50Z"
    - latency: 2.1233ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:50Z"
    - latency: 2.689927ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:12:50Z"
    - latency: 2.398399ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:11:50Z"
    - latency: 2.246347ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:10:50Z"
    - latency: 2.428323ms
      message: 'network-check-target-ip-10-0-130-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:09:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-85-to-network-check-target-ip-10-0-132-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-85.ec2.internal
      uid: 001aac4a-8052-4adc-8cf9-84da38a07aeb
    resourceVersion: "39253"
    uid: 3364ca65-ae44-4ab3-af2c-65468f13f500
  spec:
    sourcePod: network-check-source-6f8b768455-25zwg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:36:50Z"
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.178923ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:18:50Z"
    - latency: 943.992µs
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:17:50Z"
    - latency: 1.008853ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:16:50Z"
    - latency: 2.022394ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:15:50Z"
    - latency: 2.124941ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:14:50Z"
    - latency: 1.051325ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:50Z"
    - latency: 1.212606ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:12:50Z"
    - latency: 915.964µs
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:11:50Z"
    - latency: 1.081272ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:10:50Z"
    - latency: 1.170793ms
      message: 'network-check-target-ip-10-0-132-85: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:09:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-85-to-network-check-target-ip-10-0-141-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-85.ec2.internal
      uid: 001aac4a-8052-4adc-8cf9-84da38a07aeb
    resourceVersion: "39254"
    uid: d587f7a8-d292-49b2-b755-e35c001ae015
  spec:
    sourcePod: network-check-source-6f8b768455-25zwg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:36:50Z"
      message: 'network-check-target-ip-10-0-141-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.225495ms
      message: 'network-check-target-ip-10-0-141-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:18:50Z"
    - latency: 2.156814ms
      message: 'network-check-target-ip-10-0-141-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:17:50Z"
    - latency: 2.41866ms
      message: 'network-check-target-ip-10-0-141-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:16:50Z"
    - latency: 2.39581ms
      message: 'network-check-target-ip-10-0-141-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:15:50Z"
    - latency: 2.085205ms
      message: 'network-check-target-ip-10-0-141-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:14:50Z"
    - latency: 2.227965ms
      message: 'network-check-target-ip-10-0-141-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:50Z"
    - latency: 2.069953ms
      message: 'network-check-target-ip-10-0-141-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:12:50Z"
    - latency: 2.345785ms
      message: 'network-check-target-ip-10-0-141-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:11:50Z"
    - latency: 2.383332ms
      message: 'network-check-target-ip-10-0-141-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:10:50Z"
    - latency: 2.415213ms
      message: 'network-check-target-ip-10-0-141-27: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:09:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T16:29:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-85-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-85.ec2.internal
      uid: 001aac4a-8052-4adc-8cf9-84da38a07aeb
    resourceVersion: "38821"
    uid: 40fc8d0b-9061-4995-b4fd-909704e6b293
  spec:
    sourcePod: network-check-source-6f8b768455-25zwg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T16:35:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.00325ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:17:50Z"
    - latency: 2.159697ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:17:50Z"
    - latency: 1.31379ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:16:50Z"
    - latency: 2.035088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:16:50Z"
    - latency: 1.077705ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:15:50Z"
    - latency: 1.913211ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:15:50Z"
    - latency: 911.414µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:14:50Z"
    - latency: 2.150608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:14:50Z"
    - latency: 1.066914ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T17:13:50Z"
    - latency: 2.039793ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T17:13:50Z"
kind: List
metadata:
  resourceVersion: ""