apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-151-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-151.ec2.internal
      uid: e6f9a770-2a9e-4355-93b3-b7cfa689fdcd
    resourceVersion: "54361"
    uid: 63ff921c-db6b-4452-8dd4-c41bb9a4329d
  spec:
    sourcePod: network-check-source-6f8b768455-w6jvn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 981.418µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:50Z"
    - latency: 1.462185ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:50Z"
    - latency: 887.562µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:50Z"
    - latency: 1.541122ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:50Z"
    - latency: 994.003µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:50Z"
    - latency: 928.875µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:50Z"
    - latency: 842.48µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:50Z"
    - latency: 1.890495ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:50Z"
    - latency: 1.166328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:50Z"
    - latency: 923.475µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:19:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-151-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-151.ec2.internal
      uid: e6f9a770-2a9e-4355-93b3-b7cfa689fdcd
    resourceVersion: "56122"
    uid: 51bc12b9-0338-4015-883a-aa31db4655ca
  spec:
    sourcePod: network-check-source-6f8b768455-w6jvn
    targetEndpoint: a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:06:50Z"
      message: 'load-balancer-api-external: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.621017ms
      message: 'load-balancer-api-external: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:50Z"
    - latency: 7.477095ms
      message: 'load-balancer-api-external: resolved host name a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:50Z"
    - latency: 5.461652ms
      message: 'load-balancer-api-external: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:50Z"
    - latency: 7.074917ms
      message: 'load-balancer-api-external: resolved host name a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:50Z"
    - latency: 3.831803ms
      message: 'load-balancer-api-external: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:50Z"
    - latency: 8.646582ms
      message: 'load-balancer-api-external: resolved host name a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:50Z"
    - latency: 6.242969ms
      message: 'load-balancer-api-external: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:50Z"
    - latency: 7.600366ms
      message: 'load-balancer-api-external: resolved host name a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:50Z"
    - latency: 3.61933ms
      message: 'load-balancer-api-external: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:50Z"
    - latency: 7.270075ms
      message: 'load-balancer-api-external: resolved host name a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:26:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-151-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-151.ec2.internal
      uid: e6f9a770-2a9e-4355-93b3-b7cfa689fdcd
    resourceVersion: "56123"
    uid: 5f5911b8-db3b-4618-acff-10c8888e9112
  spec:
    sourcePod: network-check-source-6f8b768455-w6jvn
    targetEndpoint: a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:06:50Z"
      message: 'load-balancer-api-internal: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.189242ms
      message: 'load-balancer-api-internal: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:50Z"
    - latency: 7.441044ms
      message: 'load-balancer-api-internal: resolved host name a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:50Z"
    - latency: 5.482629ms
      message: 'load-balancer-api-internal: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:50Z"
    - latency: 7.027395ms
      message: 'load-balancer-api-internal: resolved host name a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:50Z"
    - latency: 3.859506ms
      message: 'load-balancer-api-internal: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:50Z"
    - latency: 8.61667ms
      message: 'load-balancer-api-internal: resolved host name a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:50Z"
    - latency: 6.235463ms
      message: 'load-balancer-api-internal: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:50Z"
    - latency: 7.566303ms
      message: 'load-balancer-api-internal: resolved host name a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:50Z"
    - latency: 4.240613ms
      message: 'load-balancer-api-internal: tcp connection to a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:50Z"
    - latency: 7.231904ms
      message: 'load-balancer-api-internal: resolved host name a4f00be50a50d48b8abff480febd15d6-8671a6f4a92752e4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:26:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-151-to-network-check-target-ip-10-0-135-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-151.ec2.internal
      uid: e6f9a770-2a9e-4355-93b3-b7cfa689fdcd
    resourceVersion: "54359"
    uid: ce5a6119-5e80-4af4-97b4-034eed1593d5
  spec:
    sourcePod: network-check-source-6f8b768455-w6jvn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:50Z"
      message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.007283ms
      message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:50Z"
    - latency: 2.471451ms
      message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:50Z"
    - latency: 2.001001ms
      message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:50Z"
    - latency: 2.870784ms
      message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:50Z"
    - latency: 2.671602ms
      message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:50Z"
    - latency: 2.545973ms
      message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:50Z"
    - latency: 2.52408ms
      message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:50Z"
    - latency: 1.725677ms
      message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:50Z"
    - latency: 2.051123ms
      message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:50Z"
    - latency: 2.024345ms
      message: 'network-check-target-ip-10-0-135-116: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:19:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-151-to-network-check-target-ip-10-0-135-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-151.ec2.internal
      uid: e6f9a770-2a9e-4355-93b3-b7cfa689fdcd
    resourceVersion: "54360"
    uid: 8612b4f0-5441-4c0b-b902-82c4bfc76a91
  spec:
    sourcePod: network-check-source-6f8b768455-w6jvn
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:50Z"
      message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.276172ms
      message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:50Z"
    - latency: 2.040157ms
      message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:50Z"
    - latency: 1.737949ms
      message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:50Z"
    - latency: 2.229787ms
      message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:50Z"
    - latency: 2.246745ms
      message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:50Z"
    - latency: 2.163369ms
      message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:50Z"
    - latency: 2.030629ms
      message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:50Z"
    - latency: 1.825361ms
      message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:50Z"
    - latency: 2.782277ms
      message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:50Z"
    - latency: 2.225672ms
      message: 'network-check-target-ip-10-0-135-61: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:19:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-151-to-network-check-target-ip-10-0-136-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-151.ec2.internal
      uid: e6f9a770-2a9e-4355-93b3-b7cfa689fdcd
    resourceVersion: "54358"
    uid: 7b35a6f2-992f-475a-aedd-5645e02ebe87
  spec:
    sourcePod: network-check-source-6f8b768455-w6jvn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:07:50Z"
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 894.888µs
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:50Z"
    - latency: 802.791µs
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:50Z"
    - latency: 884.828µs
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:50Z"
    - latency: 2.126545ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:25:50Z"
    - latency: 951.731µs
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:24:50Z"
    - latency: 1.488658ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:23:50Z"
    - latency: 1.436261ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:22:50Z"
    - latency: 882.497µs
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:21:50Z"
    - latency: 1.645486ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:20:50Z"
    - latency: 1.057594ms
      message: 'network-check-target-ip-10-0-136-151: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:19:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T21:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-151-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-151.ec2.internal
      uid: e6f9a770-2a9e-4355-93b3-b7cfa689fdcd
    resourceVersion: "56121"
    uid: 84d200c8-182b-40ce-adca-9691e7996ae9
  spec:
    sourcePod: network-check-source-6f8b768455-w6jvn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T21:06:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026975ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:30:50Z"
    - latency: 1.888325ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:30:50Z"
    - latency: 1.200001ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:29:50Z"
    - latency: 1.798299ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:29:50Z"
    - latency: 849.66µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:28:50Z"
    - latency: 1.989285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:28:50Z"
    - latency: 1.316809ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:27:50Z"
    - latency: 1.984478ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:27:50Z"
    - latency: 1.018158ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:26:50Z"
    - latency: 1.843948ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:26:50Z"
kind: List
metadata:
  resourceVersion: ""