apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:24:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-227-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-227.ec2.internal
      uid: 31419034-98f9-4690-8688-eba35605d045
    resourceVersion: "65194"
    uid: 957cfb20-cacd-4960-9ab6-31afbbbf6f0d
  spec:
    sourcePod: network-check-source-7d88cb55d8-m7lml
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:31:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.649806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:46Z"
    - latency: 959.205µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:46Z"
    - latency: 894.889µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:04:46Z"
    - latency: 933.633µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:03:46Z"
    - latency: 1.123467ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:02:46Z"
    - latency: 1.276769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:01:46Z"
    - latency: 959.81µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:00:46Z"
    - latency: 1.303714ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:59:46Z"
    - latency: 1.357879ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:58:46Z"
    - latency: 1.023841ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:57:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:24:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-227-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-227.ec2.internal
      uid: 31419034-98f9-4690-8688-eba35605d045
    resourceVersion: "65196"
    uid: 8d07a12f-329b-4da6-baad-5f25b944cd6f
  spec:
    sourcePod: network-check-source-7d88cb55d8-m7lml
    targetEndpoint: afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:30:46Z"
      message: 'load-balancer-api-external: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.837334ms
      message: 'load-balancer-api-external: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:46Z"
    - latency: 9.565579ms
      message: 'load-balancer-api-external: resolved host name afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:06:46Z"
    - latency: 5.331864ms
      message: 'load-balancer-api-external: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:46Z"
    - latency: 7.780376ms
      message: 'load-balancer-api-external: resolved host name afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:05:46Z"
    - latency: 4.828038ms
      message: 'load-balancer-api-external: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:04:46Z"
    - latency: 10.144706ms
      message: 'load-balancer-api-external: resolved host name afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:04:46Z"
    - latency: 3.885862ms
      message: 'load-balancer-api-external: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:03:46Z"
    - latency: 9.622938ms
      message: 'load-balancer-api-external: resolved host name afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:03:46Z"
    - latency: 3.653538ms
      message: 'load-balancer-api-external: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:02:46Z"
    - latency: 8.434202ms
      message: 'load-balancer-api-external: resolved host name afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:02:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:24:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-227-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-227.ec2.internal
      uid: 31419034-98f9-4690-8688-eba35605d045
    resourceVersion: "65195"
    uid: a83745d4-b1d7-4836-b7e4-c9279d8c8cc3
  spec:
    sourcePod: network-check-source-7d88cb55d8-m7lml
    targetEndpoint: afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:30:46Z"
      message: 'load-balancer-api-internal: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.799431ms
      message: 'load-balancer-api-internal: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:46Z"
    - latency: 9.696979ms
      message: 'load-balancer-api-internal: resolved host name afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:06:46Z"
    - latency: 5.286277ms
      message: 'load-balancer-api-internal: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:46Z"
    - latency: 7.717236ms
      message: 'load-balancer-api-internal: resolved host name afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:05:46Z"
    - latency: 4.841001ms
      message: 'load-balancer-api-internal: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:04:46Z"
    - latency: 10.019766ms
      message: 'load-balancer-api-internal: resolved host name afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:04:46Z"
    - latency: 3.889496ms
      message: 'load-balancer-api-internal: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:03:46Z"
    - latency: 9.573556ms
      message: 'load-balancer-api-internal: resolved host name afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:03:46Z"
    - latency: 3.716813ms
      message: 'load-balancer-api-internal: tcp connection to afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:02:46Z"
    - latency: 8.386544ms
      message: 'load-balancer-api-internal: resolved host name afa914981ce814bf598f1e64fc2de6c3-79cc5b298f5b923f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:02:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:24:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-227-to-network-check-target-ip-10-0-132-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-227.ec2.internal
      uid: 31419034-98f9-4690-8688-eba35605d045
    resourceVersion: "65193"
    uid: 0fdcb208-42fd-4e1c-9127-7a15c41acd1f
  spec:
    sourcePod: network-check-source-7d88cb55d8-m7lml
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:31:46Z"
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.998921ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:46Z"
    - latency: 2.641982ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:46Z"
    - latency: 2.427753ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:04:46Z"
    - latency: 3.165503ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:03:46Z"
    - latency: 2.695635ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:02:46Z"
    - latency: 2.495178ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:01:46Z"
    - latency: 2.604601ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:00:46Z"
    - latency: 2.401ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:59:46Z"
    - latency: 2.772557ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:58:46Z"
    - latency: 2.446309ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:57:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:24:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-227-to-network-check-target-ip-10-0-134-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-227.ec2.internal
      uid: 31419034-98f9-4690-8688-eba35605d045
    resourceVersion: "65191"
    uid: c44bab30-e948-45cd-bac7-ccda74ac34c0
  spec:
    sourcePod: network-check-source-7d88cb55d8-m7lml
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:31:46Z"
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.177564ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:46Z"
    - latency: 2.268626ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:46Z"
    - latency: 2.745675ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:04:46Z"
    - latency: 2.568783ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:03:46Z"
    - latency: 2.409482ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:02:46Z"
    - latency: 2.529746ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:01:46Z"
    - latency: 2.502168ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:00:46Z"
    - latency: 2.35255ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:59:46Z"
    - latency: 2.892025ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:58:46Z"
    - latency: 2.287813ms
      message: 'network-check-target-ip-10-0-134-147: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:57:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:24:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-227-to-network-check-target-ip-10-0-140-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-227.ec2.internal
      uid: 31419034-98f9-4690-8688-eba35605d045
    resourceVersion: "65190"
    uid: a26c11b4-7432-4ab8-b60d-0bb5aa425d04
  spec:
    sourcePod: network-check-source-7d88cb55d8-m7lml
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:31:46Z"
      message: 'network-check-target-ip-10-0-140-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.15833ms
      message: 'network-check-target-ip-10-0-140-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:46Z"
    - latency: 1.29512ms
      message: 'network-check-target-ip-10-0-140-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:46Z"
    - latency: 952.415µs
      message: 'network-check-target-ip-10-0-140-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:04:46Z"
    - latency: 1.708883ms
      message: 'network-check-target-ip-10-0-140-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:03:46Z"
    - latency: 1.725625ms
      message: 'network-check-target-ip-10-0-140-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:02:46Z"
    - latency: 1.173273ms
      message: 'network-check-target-ip-10-0-140-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:01:46Z"
    - latency: 920.247µs
      message: 'network-check-target-ip-10-0-140-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:00:46Z"
    - latency: 1.070326ms
      message: 'network-check-target-ip-10-0-140-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:59:46Z"
    - latency: 2.096838ms
      message: 'network-check-target-ip-10-0-140-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:58:46Z"
    - latency: 1.078368ms
      message: 'network-check-target-ip-10-0-140-227: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T03:57:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T03:24:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-227-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-227.ec2.internal
      uid: 31419034-98f9-4690-8688-eba35605d045
    resourceVersion: "65192"
    uid: 0e5ebd27-c653-428d-aebd-92696757e327
  spec:
    sourcePod: network-check-source-7d88cb55d8-m7lml
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T03:30:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.091784ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:06:46Z"
    - latency: 1.958489ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:06:46Z"
    - latency: 973.774µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:05:46Z"
    - latency: 1.975683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:05:46Z"
    - latency: 864.155µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:04:46Z"
    - latency: 2.489719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:04:46Z"
    - latency: 1.54351ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:03:46Z"
    - latency: 2.262919ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:03:46Z"
    - latency: 974.273µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T04:02:46Z"
    - latency: 2.694882ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T04:02:46Z"
kind: List
metadata:
  resourceVersion: ""