apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T00:12:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-185-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-185.ec2.internal
      uid: b8a0bccf-4bdb-4e10-9055-83b3c8de0aec
    resourceVersion: "29749"
    uid: e00254cb-aa84-4698-a88e-c6f4f4b04c40
  spec:
    sourcePod: network-check-source-989f8b8dc-z2z4n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T00:20:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 938.901µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:27:00Z"
    - latency: 1.605542ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:26:00Z"
    - latency: 942.512µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:25:00Z"
    - latency: 994.018µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:24:00Z"
    - latency: 1.318915ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:23:00Z"
    - latency: 987.381µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:22:00Z"
    - latency: 1.330566ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:21:00Z"
    - latency: 926.337µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:20:00Z"
    - latency: 879.909µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:19:00Z"
    - latency: 918.27µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:18:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T00:12:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-185-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-185.ec2.internal
      uid: b8a0bccf-4bdb-4e10-9055-83b3c8de0aec
    resourceVersion: "32632"
    uid: e3d8bfef-f7e6-4fff-838d-8cba6bdc2a24
  spec:
    sourcePod: network-check-source-989f8b8dc-z2z4n
    targetEndpoint: a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T00:19:00Z"
      message: 'load-balancer-api-external: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.884534ms
      message: 'load-balancer-api-external: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:31:00Z"
    - latency: 6.892897ms
      message: 'load-balancer-api-external: resolved host name a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:31:00Z"
    - latency: 3.689857ms
      message: 'load-balancer-api-external: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:30:00Z"
    - latency: 7.309381ms
      message: 'load-balancer-api-external: resolved host name a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:30:00Z"
    - latency: 4.567266ms
      message: 'load-balancer-api-external: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:29:00Z"
    - latency: 7.064148ms
      message: 'load-balancer-api-external: resolved host name a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:29:00Z"
    - latency: 5.130432ms
      message: 'load-balancer-api-external: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:28:00Z"
    - latency: 6.520523ms
      message: 'load-balancer-api-external: resolved host name a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:28:00Z"
    - latency: 5.031273ms
      message: 'load-balancer-api-external: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:27:00Z"
    - latency: 6.282318ms
      message: 'load-balancer-api-external: resolved host name a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:27:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T00:12:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-185-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-185.ec2.internal
      uid: b8a0bccf-4bdb-4e10-9055-83b3c8de0aec
    resourceVersion: "32631"
    uid: ea1b8f90-781c-4301-a69c-cf093241e747
  spec:
    sourcePod: network-check-source-989f8b8dc-z2z4n
    targetEndpoint: a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T00:19:00Z"
      message: 'load-balancer-api-internal: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.545777ms
      message: 'load-balancer-api-internal: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:31:00Z"
    - latency: 6.970482ms
      message: 'load-balancer-api-internal: resolved host name a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:31:00Z"
    - latency: 4.303229ms
      message: 'load-balancer-api-internal: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:30:00Z"
    - latency: 7.237736ms
      message: 'load-balancer-api-internal: resolved host name a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:30:00Z"
    - latency: 4.88345ms
      message: 'load-balancer-api-internal: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:29:00Z"
    - latency: 6.960676ms
      message: 'load-balancer-api-internal: resolved host name a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:29:00Z"
    - latency: 4.878658ms
      message: 'load-balancer-api-internal: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:28:00Z"
    - latency: 6.457084ms
      message: 'load-balancer-api-internal: resolved host name a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:28:00Z"
    - latency: 7.358343ms
      message: 'load-balancer-api-internal: tcp connection to a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:27:00Z"
    - latency: 6.22162ms
      message: 'load-balancer-api-internal: resolved host name a03aef35a35254d379ebfd080ea93736-020eac87e2e37aa5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:27:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T00:12:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-185-to-network-check-target-ip-10-0-128-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-185.ec2.internal
      uid: b8a0bccf-4bdb-4e10-9055-83b3c8de0aec
    resourceVersion: "29747"
    uid: fee85249-8949-4529-8560-f720ac02e094
  spec:
    sourcePod: network-check-source-989f8b8dc-z2z4n
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T00:20:00Z"
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.486867ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:27:00Z"
    - latency: 2.259037ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:26:00Z"
    - latency: 2.215803ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:25:00Z"
    - latency: 2.265336ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:24:00Z"
    - latency: 2.206892ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:23:00Z"
    - latency: 2.308727ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:22:00Z"
    - latency: 2.418984ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:21:00Z"
    - latency: 2.011129ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:20:00Z"
    - latency: 2.18406ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:19:00Z"
    - latency: 2.308284ms
      message: 'network-check-target-ip-10-0-128-26: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:18:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T00:12:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-185-to-network-check-target-ip-10-0-132-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-185.ec2.internal
      uid: b8a0bccf-4bdb-4e10-9055-83b3c8de0aec
    resourceVersion: "29748"
    uid: ca75272e-c102-412e-85f6-06ccfa52da3f
  spec:
    sourcePod: network-check-source-989f8b8dc-z2z4n
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T00:20:00Z"
      message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.179678ms
      message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:27:00Z"
    - latency: 2.187869ms
      message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:26:00Z"
    - latency: 2.177799ms
      message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:25:00Z"
    - latency: 2.490383ms
      message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:24:00Z"
    - latency: 2.283169ms
      message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:23:00Z"
    - latency: 2.178618ms
      message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:22:00Z"
    - latency: 2.19895ms
      message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:21:00Z"
    - latency: 2.133264ms
      message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:20:00Z"
    - latency: 2.169414ms
      message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:19:00Z"
    - latency: 2.271055ms
      message: 'network-check-target-ip-10-0-132-216: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:18:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T00:12:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-185-to-network-check-target-ip-10-0-138-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-185.ec2.internal
      uid: b8a0bccf-4bdb-4e10-9055-83b3c8de0aec
    resourceVersion: "29746"
    uid: 054bec8f-4fb8-4299-bcfb-a144a7660ea4
  spec:
    sourcePod: network-check-source-989f8b8dc-z2z4n
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T00:20:00Z"
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.61µs
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:27:00Z"
    - latency: 1.023186ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:26:00Z"
    - latency: 1.170306ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:25:00Z"
    - latency: 1.138363ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:24:00Z"
    - latency: 1.563341ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:23:00Z"
    - latency: 919.415µs
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:22:00Z"
    - latency: 868.069µs
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:21:00Z"
    - latency: 924.789µs
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:20:00Z"
    - latency: 1.228137ms
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:19:00Z"
    - latency: 723.19µs
      message: 'network-check-target-ip-10-0-138-185: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:18:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T00:12:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-185-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-185.ec2.internal
      uid: b8a0bccf-4bdb-4e10-9055-83b3c8de0aec
    resourceVersion: "32630"
    uid: 1edcdb40-b558-4e39-b32b-f9d52fa66ade
  spec:
    sourcePod: network-check-source-989f8b8dc-z2z4n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T00:19:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.0427ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:31:00Z"
    - latency: 1.939822ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:31:00Z"
    - latency: 771.27µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:30:00Z"
    - latency: 2.3594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:30:00Z"
    - latency: 1.075183ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:29:00Z"
    - latency: 1.646961ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:29:00Z"
    - latency: 1.019809ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:28:00Z"
    - latency: 1.603612ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:28:00Z"
    - latency: 857.633µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T00:27:00Z"
    - latency: 1.814717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T00:27:00Z"
kind: List
metadata:
  resourceVersion: ""