apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 909506ea-9972-4cb7-af8d-c46452d04079
    resourceVersion: "52805"
    uid: c86ee135-241a-4878-8301-f5f16a10fc23
  spec:
    sourcePod: network-check-source-685456655f-mnjbb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:06:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 932.087µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:27:23Z"
    - latency: 860.936µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:26:23Z"
    - latency: 857.112µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:25:23Z"
    - latency: 886.688µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:24:23Z"
    - latency: 1.368875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:23:23Z"
    - latency: 1.062099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:22:23Z"
    - latency: 775.211µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:21:23Z"
    - latency: 1.775117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:20:23Z"
    - latency: 966.467µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:19:23Z"
    - latency: 1.115475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:18:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 909506ea-9972-4cb7-af8d-c46452d04079
    resourceVersion: "54704"
    uid: e404f691-f8e5-440f-a068-8959fadcefae
  spec:
    sourcePod: network-check-source-685456655f-mnjbb
    targetEndpoint: a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:05:23Z"
      message: 'load-balancer-api-external: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.859337ms
      message: 'load-balancer-api-external: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:29:23Z"
    - latency: 7.382202ms
      message: 'load-balancer-api-external: resolved host name a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:29:23Z"
    - latency: 5.315676ms
      message: 'load-balancer-api-external: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:28:23Z"
    - latency: 6.42734ms
      message: 'load-balancer-api-external: resolved host name a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:28:23Z"
    - latency: 4.73081ms
      message: 'load-balancer-api-external: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:27:23Z"
    - latency: 7.373247ms
      message: 'load-balancer-api-external: resolved host name a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:27:23Z"
    - latency: 4.069594ms
      message: 'load-balancer-api-external: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:26:23Z"
    - latency: 7.120104ms
      message: 'load-balancer-api-external: resolved host name a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:26:23Z"
    - latency: 5.55896ms
      message: 'load-balancer-api-external: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:25:23Z"
    - latency: 7.499409ms
      message: 'load-balancer-api-external: resolved host name a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:25:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 909506ea-9972-4cb7-af8d-c46452d04079
    resourceVersion: "54705"
    uid: 90fec31c-8df0-4139-8382-f292db9b7c2d
  spec:
    sourcePod: network-check-source-685456655f-mnjbb
    targetEndpoint: a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:05:23Z"
      message: 'load-balancer-api-internal: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.799436ms
      message: 'load-balancer-api-internal: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:29:23Z"
    - latency: 7.481162ms
      message: 'load-balancer-api-internal: resolved host name a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:29:23Z"
    - latency: 5.310087ms
      message: 'load-balancer-api-internal: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:28:23Z"
    - latency: 6.473343ms
      message: 'load-balancer-api-internal: resolved host name a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:28:23Z"
    - latency: 3.100114ms
      message: 'load-balancer-api-internal: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:27:23Z"
    - latency: 7.430479ms
      message: 'load-balancer-api-internal: resolved host name a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:27:23Z"
    - latency: 4.0342ms
      message: 'load-balancer-api-internal: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:26:23Z"
    - latency: 7.149831ms
      message: 'load-balancer-api-internal: resolved host name a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:26:23Z"
    - latency: 5.585158ms
      message: 'load-balancer-api-internal: tcp connection to a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:25:23Z"
    - latency: 7.533097ms
      message: 'load-balancer-api-internal: resolved host name a180ad2b90363402289452fab9920906-d170e736a64b4892.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:25:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-network-check-target-ip-10-0-128-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 909506ea-9972-4cb7-af8d-c46452d04079
    resourceVersion: "52804"
    uid: c1c625b5-dd8b-41f6-b5db-87d378d9cfd2
  spec:
    sourcePod: network-check-source-685456655f-mnjbb
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:06:23Z"
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.061286ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:27:23Z"
    - latency: 1.989989ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:26:23Z"
    - latency: 2.527539ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:25:23Z"
    - latency: 2.349014ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:24:23Z"
    - latency: 2.672473ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:23:23Z"
    - latency: 2.192638ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:22:23Z"
    - latency: 1.948757ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:21:23Z"
    - latency: 2.31823ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:20:23Z"
    - latency: 2.024601ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:19:23Z"
    - latency: 2.190531ms
      message: 'network-check-target-ip-10-0-128-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:18:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-network-check-target-ip-10-0-131-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 909506ea-9972-4cb7-af8d-c46452d04079
    resourceVersion: "52803"
    uid: a42e2123-d6e7-45f8-9bd2-ba1d8aa05a4c
  spec:
    sourcePod: network-check-source-685456655f-mnjbb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:06:23Z"
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 909.784µs
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:27:23Z"
    - latency: 865.078µs
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:26:23Z"
    - latency: 1.78563ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:25:23Z"
    - latency: 1.027283ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:24:23Z"
    - latency: 939.937µs
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:23:23Z"
    - latency: 1.504123ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:22:23Z"
    - latency: 1.733278ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:21:23Z"
    - latency: 963.066µs
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:20:23Z"
    - latency: 1.122554ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:19:23Z"
    - latency: 1.236168ms
      message: 'network-check-target-ip-10-0-131-84: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:18:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-network-check-target-ip-10-0-136-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 909506ea-9972-4cb7-af8d-c46452d04079
    resourceVersion: "52802"
    uid: 92b13bb6-9176-44d7-853e-adc50e71ce92
  spec:
    sourcePod: network-check-source-685456655f-mnjbb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:06:23Z"
      message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.872341ms
      message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:27:23Z"
    - latency: 1.828263ms
      message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:26:23Z"
    - latency: 2.156605ms
      message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:25:23Z"
    - latency: 1.812244ms
      message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:24:23Z"
    - latency: 2.306445ms
      message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:23:23Z"
    - latency: 1.808168ms
      message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:22:23Z"
    - latency: 1.44701ms
      message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:21:23Z"
    - latency: 1.807701ms
      message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:20:23Z"
    - latency: 2.071897ms
      message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:19:23Z"
    - latency: 1.912423ms
      message: 'network-check-target-ip-10-0-136-3: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:18:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:59:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-84-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-84.ec2.internal
      uid: 909506ea-9972-4cb7-af8d-c46452d04079
    resourceVersion: "54703"
    uid: 12e09211-4568-47f6-84ff-cce3c2742b4b
  spec:
    sourcePod: network-check-source-685456655f-mnjbb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T17:05:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 776.177µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:29:23Z"
    - latency: 2.335772ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:29:23Z"
    - latency: 958.356µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:28:23Z"
    - latency: 1.96147ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:28:23Z"
    - latency: 828.466µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:27:23Z"
    - latency: 1.888372ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:27:23Z"
    - latency: 825.583µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:26:23Z"
    - latency: 2.107902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:26:23Z"
    - latency: 772.193µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T17:25:23Z"
    - latency: 2.038096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T17:25:23Z"
kind: List
metadata:
  resourceVersion: ""