apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:56:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-93-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-93.ec2.internal
      uid: db71f283-275e-4774-8080-91ed756d2086
    resourceVersion: "54434"
    uid: b82e7c4b-0146-4ca9-8f4a-cd16cf8743f4
  spec:
    sourcePod: network-check-source-869dcfcdcd-ncr7h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:03:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.674µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:29Z"
    - latency: 1.359443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:30:29Z"
    - latency: 1.614902ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:29:29Z"
    - latency: 1.146651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:28:29Z"
    - latency: 1.173309ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:27:29Z"
    - latency: 1.211548ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:26:29Z"
    - latency: 1.038874ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:29Z"
    - latency: 1.11359ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:29Z"
    - latency: 1.21709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:29Z"
    - latency: 1.206399ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:56:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-93-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-93.ec2.internal
      uid: db71f283-275e-4774-8080-91ed756d2086
    resourceVersion: "55490"
    uid: 78ead5c6-72bf-4dfb-b9e6-aa012c543bc5
  spec:
    sourcePod: network-check-source-869dcfcdcd-ncr7h
    targetEndpoint: af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:02:29Z"
      message: 'load-balancer-api-external: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.334279ms
      message: 'load-balancer-api-external: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:32:29Z"
    - latency: 7.642552ms
      message: 'load-balancer-api-external: resolved host name af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:32:29Z"
    - latency: 5.357304ms
      message: 'load-balancer-api-external: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:29Z"
    - latency: 7.944281ms
      message: 'load-balancer-api-external: resolved host name af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:31:29Z"
    - latency: 4.439651ms
      message: 'load-balancer-api-external: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:30:29Z"
    - latency: 6.652737ms
      message: 'load-balancer-api-external: resolved host name af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:30:29Z"
    - latency: 4.704845ms
      message: 'load-balancer-api-external: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:29:29Z"
    - latency: 7.482267ms
      message: 'load-balancer-api-external: resolved host name af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:29:29Z"
    - latency: 5.789258ms
      message: 'load-balancer-api-external: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:28:29Z"
    - latency: 7.132232ms
      message: 'load-balancer-api-external: resolved host name af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:28:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:56:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-93-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-93.ec2.internal
      uid: db71f283-275e-4774-8080-91ed756d2086
    resourceVersion: "55489"
    uid: e4360529-eed0-4fbe-acdc-44039fbd1e43
  spec:
    sourcePod: network-check-source-869dcfcdcd-ncr7h
    targetEndpoint: af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:02:29Z"
      message: 'load-balancer-api-internal: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.241156ms
      message: 'load-balancer-api-internal: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:32:29Z"
    - latency: 7.621849ms
      message: 'load-balancer-api-internal: resolved host name af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:32:29Z"
    - latency: 5.595066ms
      message: 'load-balancer-api-internal: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:29Z"
    - latency: 7.968653ms
      message: 'load-balancer-api-internal: resolved host name af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:31:29Z"
    - latency: 4.449485ms
      message: 'load-balancer-api-internal: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:30:29Z"
    - latency: 6.686791ms
      message: 'load-balancer-api-internal: resolved host name af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:30:29Z"
    - latency: 6.177043ms
      message: 'load-balancer-api-internal: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:29:29Z"
    - latency: 7.502188ms
      message: 'load-balancer-api-internal: resolved host name af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:29:29Z"
    - latency: 5.932798ms
      message: 'load-balancer-api-internal: tcp connection to af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:28:29Z"
    - latency: 7.241024ms
      message: 'load-balancer-api-internal: resolved host name af11bf901ca3041deb7874c00b261c56-66927591cc74beba.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:28:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:56:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-93-to-network-check-target-ip-10-0-129-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-93.ec2.internal
      uid: db71f283-275e-4774-8080-91ed756d2086
    resourceVersion: "54430"
    uid: 826fe834-0c55-4c64-93b3-c73858115775
  spec:
    sourcePod: network-check-source-869dcfcdcd-ncr7h
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:03:29Z"
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.255104ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:29Z"
    - latency: 1.622099ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:30:29Z"
    - latency: 1.79739ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:29:29Z"
    - latency: 1.14387ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:28:29Z"
    - latency: 3.080151ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:27:29Z"
    - latency: 1.452149ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:26:29Z"
    - latency: 1.17599ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:29Z"
    - latency: 1.401802ms
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:29Z"
    - latency: 928.135µs
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:29Z"
    - latency: 885.967µs
      message: 'network-check-target-ip-10-0-129-93: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:56:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-93-to-network-check-target-ip-10-0-131-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-93.ec2.internal
      uid: db71f283-275e-4774-8080-91ed756d2086
    resourceVersion: "54431"
    uid: d3a2b6d1-da63-4ccb-a678-f90396aa718e
  spec:
    sourcePod: network-check-source-869dcfcdcd-ncr7h
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:03:29Z"
      message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.211039ms
      message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:29Z"
    - latency: 2.543482ms
      message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:30:29Z"
    - latency: 1.963627ms
      message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:29:29Z"
    - latency: 1.811098ms
      message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:28:29Z"
    - latency: 1.984093ms
      message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:27:29Z"
    - latency: 2.07487ms
      message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:26:29Z"
    - latency: 1.819945ms
      message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:29Z"
    - latency: 2.004501ms
      message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:29Z"
    - latency: 2.132421ms
      message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:29Z"
    - latency: 1.976608ms
      message: 'network-check-target-ip-10-0-131-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:56:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-93-to-network-check-target-ip-10-0-133-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-93.ec2.internal
      uid: db71f283-275e-4774-8080-91ed756d2086
    resourceVersion: "54432"
    uid: 38565f8e-1f21-4055-8e6f-03f5701f51bd
  spec:
    sourcePod: network-check-source-869dcfcdcd-ncr7h
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:03:29Z"
      message: 'network-check-target-ip-10-0-133-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.226245ms
      message: 'network-check-target-ip-10-0-133-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:29Z"
    - latency: 2.439566ms
      message: 'network-check-target-ip-10-0-133-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:30:29Z"
    - latency: 2.462907ms
      message: 'network-check-target-ip-10-0-133-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:29:29Z"
    - latency: 2.355145ms
      message: 'network-check-target-ip-10-0-133-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:28:29Z"
    - latency: 2.139583ms
      message: 'network-check-target-ip-10-0-133-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:27:29Z"
    - latency: 2.2536ms
      message: 'network-check-target-ip-10-0-133-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:26:29Z"
    - latency: 2.243704ms
      message: 'network-check-target-ip-10-0-133-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:29Z"
    - latency: 2.294523ms
      message: 'network-check-target-ip-10-0-133-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:29Z"
    - latency: 2.222194ms
      message: 'network-check-target-ip-10-0-133-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:29Z"
    - latency: 2.395384ms
      message: 'network-check-target-ip-10-0-133-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:56:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-93-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-93.ec2.internal
      uid: db71f283-275e-4774-8080-91ed756d2086
    resourceVersion: "55488"
    uid: e9b32018-ba10-4f7b-b819-8d79528dc05b
  spec:
    sourcePod: network-check-source-869dcfcdcd-ncr7h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T19:02:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.285099ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:32:29Z"
    - latency: 1.914323ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:32:29Z"
    - latency: 1.075344ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:31:29Z"
    - latency: 2.289801ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:31:29Z"
    - latency: 1.021468ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:30:29Z"
    - latency: 1.943717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:30:29Z"
    - latency: 1.028631ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:29:29Z"
    - latency: 1.889902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:29:29Z"
    - latency: 1.079386ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:28:29Z"
    - latency: 1.985513ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:28:29Z"
kind: List
metadata:
  resourceVersion: ""