apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:50:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-111-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-111.ec2.internal
      uid: 2e355047-8806-4bb1-afd2-3f12eba93790
    resourceVersion: "73682"
    uid: 2172e8bb-4340-4193-9c9d-b98af0f81908
  spec:
    sourcePod: network-check-source-7d88cb55d8-hw728
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:57:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.047074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:39:40Z"
    - latency: 2.586604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:38:40Z"
    - latency: 1.081235ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:37:40Z"
    - latency: 1.677222ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:36:40Z"
    - latency: 935.982µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:35:40Z"
    - latency: 1.574778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:34:40Z"
    - latency: 1.413514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:33:40Z"
    - latency: 1.281325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:32:40Z"
    - latency: 1.01309ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:31:40Z"
    - latency: 1.347794ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:30:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:50:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-111-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-111.ec2.internal
      uid: 2e355047-8806-4bb1-afd2-3f12eba93790
    resourceVersion: "71203"
    uid: 1a34d93f-ce00-4022-a0b8-0452138fae6b
  spec:
    sourcePod: network-check-source-7d88cb55d8-hw728
    targetEndpoint: ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:56:40Z"
      message: 'load-balancer-api-external: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.631308ms
      message: 'load-balancer-api-external: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:38:40Z"
    - latency: 10.518758ms
      message: 'load-balancer-api-external: resolved host name ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:38:40Z"
    - latency: 5.381332ms
      message: 'load-balancer-api-external: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:37:40Z"
    - latency: 13.394968ms
      message: 'load-balancer-api-external: resolved host name ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:37:40Z"
    - latency: 5.012332ms
      message: 'load-balancer-api-external: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:36:40Z"
    - latency: 14.470889ms
      message: 'load-balancer-api-external: resolved host name ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:36:40Z"
    - latency: 5.941652ms
      message: 'load-balancer-api-external: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:35:40Z"
    - latency: 8.485956ms
      message: 'load-balancer-api-external: resolved host name ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:35:40Z"
    - latency: 5.670516ms
      message: 'load-balancer-api-external: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:34:40Z"
    - latency: 11.484603ms
      message: 'load-balancer-api-external: resolved host name ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:34:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:50:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-111-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-111.ec2.internal
      uid: 2e355047-8806-4bb1-afd2-3f12eba93790
    resourceVersion: "71202"
    uid: d5b106bf-783c-4ea6-9c49-d9945008a3d5
  spec:
    sourcePod: network-check-source-7d88cb55d8-hw728
    targetEndpoint: ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:56:40Z"
      message: 'load-balancer-api-internal: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.611751ms
      message: 'load-balancer-api-internal: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:38:40Z"
    - latency: 10.779476ms
      message: 'load-balancer-api-internal: resolved host name ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:38:40Z"
    - latency: 5.36674ms
      message: 'load-balancer-api-internal: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:37:40Z"
    - latency: 13.356828ms
      message: 'load-balancer-api-internal: resolved host name ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:37:40Z"
    - latency: 3.990214ms
      message: 'load-balancer-api-internal: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:36:40Z"
    - latency: 14.487284ms
      message: 'load-balancer-api-internal: resolved host name ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:36:40Z"
    - latency: 5.962909ms
      message: 'load-balancer-api-internal: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:35:40Z"
    - latency: 8.445871ms
      message: 'load-balancer-api-internal: resolved host name ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:35:40Z"
    - latency: 5.636901ms
      message: 'load-balancer-api-internal: tcp connection to ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:34:40Z"
    - latency: 11.529325ms
      message: 'load-balancer-api-internal: resolved host name ab1448eafeb1a4c7cb8110e5edb5737d-a1fa9b0c576ed1b6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:34:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:50:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-111-to-network-check-target-ip-10-0-131-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-111.ec2.internal
      uid: 2e355047-8806-4bb1-afd2-3f12eba93790
    resourceVersion: "73678"
    uid: f586ce0b-6ca7-4f20-bf36-c791b60e10a2
  spec:
    sourcePod: network-check-source-7d88cb55d8-hw728
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:57:40Z"
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.694352ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:39:40Z"
    - latency: 1.287425ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:38:40Z"
    - latency: 1.182941ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:37:40Z"
    - latency: 1.221568ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:36:40Z"
    - latency: 1.054357ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:35:40Z"
    - latency: 1.792086ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:34:40Z"
    - latency: 1.306289ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:33:40Z"
    - latency: 1.937342ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:32:40Z"
    - latency: 1.178369ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:31:40Z"
    - latency: 1.03544ms
      message: 'network-check-target-ip-10-0-131-111: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:30:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:50:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-111-to-network-check-target-ip-10-0-137-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-111.ec2.internal
      uid: 2e355047-8806-4bb1-afd2-3f12eba93790
    resourceVersion: "73679"
    uid: f9bfc4d1-5b1f-40bb-ac93-47af5d44eb6e
  spec:
    sourcePod: network-check-source-7d88cb55d8-hw728
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:57:40Z"
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.843412ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:39:40Z"
    - latency: 2.687778ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:38:40Z"
    - latency: 2.507866ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:37:40Z"
    - latency: 2.404325ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:36:40Z"
    - latency: 2.370169ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:35:40Z"
    - latency: 2.410207ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:34:40Z"
    - latency: 2.158669ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:33:40Z"
    - latency: 2.463713ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:32:40Z"
    - latency: 2.083428ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:31:40Z"
    - latency: 2.388057ms
      message: 'network-check-target-ip-10-0-137-173: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:30:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:50:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-111-to-network-check-target-ip-10-0-140-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-111.ec2.internal
      uid: 2e355047-8806-4bb1-afd2-3f12eba93790
    resourceVersion: "73680"
    uid: 144a15d0-ae16-4bdb-8b9a-f2aafeed0297
  spec:
    sourcePod: network-check-source-7d88cb55d8-hw728
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:57:40Z"
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.297628ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:39:40Z"
    - latency: 2.342548ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:38:40Z"
    - latency: 2.067289ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:37:40Z"
    - latency: 2.328238ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:36:40Z"
    - latency: 1.849086ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:35:40Z"
    - latency: 2.226099ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:34:40Z"
    - latency: 2.456569ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:33:40Z"
    - latency: 2.223085ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:32:40Z"
    - latency: 2.043669ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:31:40Z"
    - latency: 2.140132ms
      message: 'network-check-target-ip-10-0-140-154: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:30:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T00:50:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-111-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-111.ec2.internal
      uid: 2e355047-8806-4bb1-afd2-3f12eba93790
    resourceVersion: "71200"
    uid: 82c25d92-5585-4527-9658-e8b93e12c019
  spec:
    sourcePod: network-check-source-7d88cb55d8-hw728
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T00:56:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.332µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:38:40Z"
    - latency: 2.535407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:38:40Z"
    - latency: 1.017024ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:37:40Z"
    - latency: 2.821554ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:37:40Z"
    - latency: 928.278µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:36:40Z"
    - latency: 2.804786ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:36:40Z"
    - latency: 880.973µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:35:40Z"
    - latency: 2.138787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:35:40Z"
    - latency: 804.752µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T01:34:40Z"
    - latency: 2.527688ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T01:34:40Z"
kind: List
metadata:
  resourceVersion: ""