apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:37:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-142.ec2.internal
      uid: 95757655-f11b-4e06-8257-c5a38ba733f1
    resourceVersion: "30071"
    uid: 55297cea-6611-4cd1-ba0b-c2caeab0e783
  spec:
    sourcePod: network-check-source-6f78d59f99-cgrj8
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:44:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.219152ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:51:47Z"
    - latency: 923.355µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:50:47Z"
    - latency: 1.295929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:49:47Z"
    - latency: 1.381708ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:48:47Z"
    - latency: 1.071753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:47:47Z"
    - latency: 1.670956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:46:47Z"
    - latency: 1.638811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:45:47Z"
    - latency: 1.232845ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:44:47Z"
    - latency: 1.1577ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:43:47Z"
    - latency: 984.366µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:42:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:37:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-142.ec2.internal
      uid: 95757655-f11b-4e06-8257-c5a38ba733f1
    resourceVersion: "27034"
    uid: 4dbaba9a-5d1a-418d-99ef-364821bed813
  spec:
    sourcePod: network-check-source-6f78d59f99-cgrj8
    targetEndpoint: abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:43:47Z"
      message: 'load-balancer-api-external: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.493654ms
      message: 'load-balancer-api-external: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:49:47Z"
    - latency: 8.97167ms
      message: 'load-balancer-api-external: resolved host name abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:49:47Z"
    - latency: 16.101516ms
      message: 'load-balancer-api-external: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:48:47Z"
    - latency: 6.566666ms
      message: 'load-balancer-api-external: resolved host name abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:48:47Z"
    - latency: 16.572201ms
      message: 'load-balancer-api-external: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:47:47Z"
    - latency: 7.507802ms
      message: 'load-balancer-api-external: resolved host name abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:47:47Z"
    - latency: 15.288341ms
      message: 'load-balancer-api-external: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:46:47Z"
    - latency: 7.405826ms
      message: 'load-balancer-api-external: resolved host name abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:46:47Z"
    - latency: 22.247057ms
      message: 'load-balancer-api-external: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:45:47Z"
    - latency: 9.496148ms
      message: 'load-balancer-api-external: resolved host name abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:45:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:37:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-142.ec2.internal
      uid: 95757655-f11b-4e06-8257-c5a38ba733f1
    resourceVersion: "27033"
    uid: 4611638a-0923-4b66-8f49-d0e19cdddc34
  spec:
    sourcePod: network-check-source-6f78d59f99-cgrj8
    targetEndpoint: abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:43:47Z"
      message: 'load-balancer-api-internal: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 13.290882ms
      message: 'load-balancer-api-internal: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:49:47Z"
    - latency: 8.994747ms
      message: 'load-balancer-api-internal: resolved host name abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:49:47Z"
    - latency: 17.196922ms
      message: 'load-balancer-api-internal: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:48:47Z"
    - latency: 6.578512ms
      message: 'load-balancer-api-internal: resolved host name abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:48:47Z"
    - latency: 16.641049ms
      message: 'load-balancer-api-internal: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:47:47Z"
    - latency: 7.553478ms
      message: 'load-balancer-api-internal: resolved host name abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:47:47Z"
    - latency: 18.031968ms
      message: 'load-balancer-api-internal: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:46:47Z"
    - latency: 7.435002ms
      message: 'load-balancer-api-internal: resolved host name abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:46:47Z"
    - latency: 18.899316ms
      message: 'load-balancer-api-internal: tcp connection to abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:45:47Z"
    - latency: 9.560191ms
      message: 'load-balancer-api-internal: resolved host name abfc121189d9a41ec8216b0bc3d1046f-7762f45701856dfa.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:45:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:37:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-142-to-network-check-target-ip-10-0-138-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-142.ec2.internal
      uid: 95757655-f11b-4e06-8257-c5a38ba733f1
    resourceVersion: "30068"
    uid: 0364e9d6-dd66-40f4-a2f8-e6d5f31972ee
  spec:
    sourcePod: network-check-source-6f78d59f99-cgrj8
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:44:47Z"
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 949.507µs
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:51:47Z"
    - latency: 1.312442ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:50:47Z"
    - latency: 1.759817ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:49:47Z"
    - latency: 880.398µs
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:48:47Z"
    - latency: 1.098958ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:47:47Z"
    - latency: 1.033558ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:46:47Z"
    - latency: 914.923µs
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:45:47Z"
    - latency: 1.60318ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:44:47Z"
    - latency: 737.589µs
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:43:47Z"
    - latency: 1.971523ms
      message: 'network-check-target-ip-10-0-138-142: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:42:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:37:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-142-to-network-check-target-ip-10-0-138-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-142.ec2.internal
      uid: 95757655-f11b-4e06-8257-c5a38ba733f1
    resourceVersion: "30070"
    uid: e3bbbb4d-a621-4d6a-b500-ab50a14e5ae8
  spec:
    sourcePod: network-check-source-6f78d59f99-cgrj8
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:44:47Z"
      message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.622589ms
      message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:51:47Z"
    - latency: 2.655027ms
      message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:50:47Z"
    - latency: 2.076755ms
      message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:49:47Z"
    - latency: 1.75294ms
      message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:48:47Z"
    - latency: 2.460317ms
      message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:47:47Z"
    - latency: 2.71022ms
      message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:46:47Z"
    - latency: 2.342727ms
      message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:45:47Z"
    - latency: 2.283606ms
      message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:44:47Z"
    - latency: 2.070128ms
      message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:43:47Z"
    - latency: 2.966758ms
      message: 'network-check-target-ip-10-0-138-47: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:42:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:37:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-142-to-network-check-target-ip-10-0-140-219
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-142.ec2.internal
      uid: 95757655-f11b-4e06-8257-c5a38ba733f1
    resourceVersion: "30069"
    uid: 8ca70361-1948-4abc-9614-a5819afecdab
  spec:
    sourcePod: network-check-source-6f78d59f99-cgrj8
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:44:47Z"
      message: 'network-check-target-ip-10-0-140-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.570602ms
      message: 'network-check-target-ip-10-0-140-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:51:47Z"
    - latency: 2.204927ms
      message: 'network-check-target-ip-10-0-140-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:50:47Z"
    - latency: 2.721299ms
      message: 'network-check-target-ip-10-0-140-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:49:47Z"
    - latency: 1.733796ms
      message: 'network-check-target-ip-10-0-140-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:48:47Z"
    - latency: 2.858136ms
      message: 'network-check-target-ip-10-0-140-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:47:47Z"
    - latency: 2.51123ms
      message: 'network-check-target-ip-10-0-140-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:46:47Z"
    - latency: 2.318622ms
      message: 'network-check-target-ip-10-0-140-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:45:47Z"
    - latency: 2.101711ms
      message: 'network-check-target-ip-10-0-140-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:44:47Z"
    - latency: 4.375264ms
      message: 'network-check-target-ip-10-0-140-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:43:47Z"
    - latency: 2.630346ms
      message: 'network-check-target-ip-10-0-140-219: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:42:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T23:37:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-142.ec2.internal
      uid: 95757655-f11b-4e06-8257-c5a38ba733f1
    resourceVersion: "27029"
    uid: 44ffcef4-16ab-4890-917e-30d0bf12ffe2
  spec:
    sourcePod: network-check-source-6f78d59f99-cgrj8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T23:43:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.006559ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:49:47Z"
    - latency: 2.484153ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:49:47Z"
    - latency: 931.918µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:48:47Z"
    - latency: 1.995251ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:48:47Z"
    - latency: 1.195742ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:47:47Z"
    - latency: 2.086685ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:47:47Z"
    - latency: 1.263542ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:46:47Z"
    - latency: 2.327847ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:46:47Z"
    - latency: 1.131743ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T23:45:47Z"
    - latency: 1.999269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T23:45:47Z"
kind: List
metadata:
  resourceVersion: ""