apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T00:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-48-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-48.us-east-2.compute.internal
      uid: 6d1abe52-01b3-45db-bc06-ae1ce4883f26
    resourceVersion: "115580"
    uid: 35e35bd6-35f1-459e-a558-5eb78d6f3ef0
  spec:
    sourcePod: network-check-source-6f78d59f99-xqsk5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:06:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.282519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:58Z"
    - latency: 892.143µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:47:58Z"
    - latency: 1.171885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:46:58Z"
    - latency: 1.345665ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:45:58Z"
    - latency: 12.250694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:44:58Z"
    - latency: 842.942µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:43:58Z"
    - latency: 1.07331ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:42:58Z"
    - latency: 1.447454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:41:58Z"
    - latency: 1.818829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:40:58Z"
    - latency: 8.501997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:39:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T00:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-48-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-48.us-east-2.compute.internal
      uid: 6d1abe52-01b3-45db-bc06-ae1ce4883f26
    resourceVersion: "113990"
    uid: 3039069e-1b28-4ea1-97e3-8ff53db6da3b
  spec:
    sourcePod: network-check-source-6f78d59f99-xqsk5
    targetEndpoint: a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:05:58Z"
      message: 'load-balancer-api-external: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.23135ms
      message: 'load-balancer-api-external: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:47:58Z"
    - latency: 7.271549ms
      message: 'load-balancer-api-external: resolved host name a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:47:58Z"
    - latency: 8.838754ms
      message: 'load-balancer-api-external: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:46:58Z"
    - latency: 7.266941ms
      message: 'load-balancer-api-external: resolved host name a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:46:58Z"
    - latency: 4.901284ms
      message: 'load-balancer-api-external: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:45:58Z"
    - latency: 6.820276ms
      message: 'load-balancer-api-external: resolved host name a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:45:58Z"
    - latency: 6.033201ms
      message: 'load-balancer-api-external: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:44:58Z"
    - latency: 22.368545ms
      message: 'load-balancer-api-external: resolved host name a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:44:58Z"
    - latency: 5.017127ms
      message: 'load-balancer-api-external: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:43:58Z"
    - latency: 6.372677ms
      message: 'load-balancer-api-external: resolved host name a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:43:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T00:59:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-48-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-48.us-east-2.compute.internal
      uid: 6d1abe52-01b3-45db-bc06-ae1ce4883f26
    resourceVersion: "113991"
    uid: b0b7426e-91fb-4e64-928a-d943377880e1
  spec:
    sourcePod: network-check-source-6f78d59f99-xqsk5
    targetEndpoint: a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:05:58Z"
      message: 'load-balancer-api-internal: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.27564ms
      message: 'load-balancer-api-internal: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:47:58Z"
    - latency: 7.201078ms
      message: 'load-balancer-api-internal: resolved host name a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:47:58Z"
    - latency: 6.562182ms
      message: 'load-balancer-api-internal: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:46:58Z"
    - latency: 7.218976ms
      message: 'load-balancer-api-internal: resolved host name a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:46:58Z"
    - latency: 5.676965ms
      message: 'load-balancer-api-internal: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:45:58Z"
    - latency: 6.716205ms
      message: 'load-balancer-api-internal: resolved host name a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:45:58Z"
    - latency: 6.041989ms
      message: 'load-balancer-api-internal: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:44:58Z"
    - latency: 22.218783ms
      message: 'load-balancer-api-internal: resolved host name a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:44:58Z"
    - latency: 4.918952ms
      message: 'load-balancer-api-internal: tcp connection to a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:43:58Z"
    - latency: 6.332025ms
      message: 'load-balancer-api-internal: resolved host name a9d643281ae1b4543962178be8914625-d7a8277f4611c85a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:43:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T00:59:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-48-to-network-check-target-ip-10-0-128-129
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-48.us-east-2.compute.internal
      uid: 6d1abe52-01b3-45db-bc06-ae1ce4883f26
    resourceVersion: "115579"
    uid: edc3191f-ffc6-4feb-abee-446d8513e7ca
  spec:
    sourcePod: network-check-source-6f78d59f99-xqsk5
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:06:58Z"
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.401243ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:58Z"
    - latency: 1.873543ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:47:58Z"
    - latency: 2.403115ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:46:58Z"
    - latency: 2.375129ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:45:58Z"
    - latency: 12.927016ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:44:58Z"
    - latency: 2.110687ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:43:58Z"
    - latency: 2.426972ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:42:58Z"
    - latency: 2.181371ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:41:58Z"
    - latency: 2.183943ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:40:58Z"
    - latency: 9.451264ms
      message: 'network-check-target-ip-10-0-128-129: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:39:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T00:59:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-48-to-network-check-target-ip-10-0-137-48
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-48.us-east-2.compute.internal
      uid: 6d1abe52-01b3-45db-bc06-ae1ce4883f26
    resourceVersion: "115577"
    uid: 3096781c-0b53-48f6-a262-a3c981a83af5
  spec:
    sourcePod: network-check-source-6f78d59f99-xqsk5
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:06:58Z"
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.504363ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:58Z"
    - latency: 1.023933ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:47:58Z"
    - latency: 1.308902ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:46:58Z"
    - latency: 998.306µs
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:45:58Z"
    - latency: 2.818397ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:44:58Z"
    - latency: 824.715µs
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:43:58Z"
    - latency: 1.388896ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:42:58Z"
    - latency: 1.372689ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:41:58Z"
    - latency: 1.277193ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:40:58Z"
    - latency: 2.609483ms
      message: 'network-check-target-ip-10-0-137-48: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:39:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T00:59:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-48-to-network-check-target-ip-10-0-140-241
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-48.us-east-2.compute.internal
      uid: 6d1abe52-01b3-45db-bc06-ae1ce4883f26
    resourceVersion: "115578"
    uid: 9053f78a-36dc-451a-99f8-c355d2be0142
  spec:
    sourcePod: network-check-source-6f78d59f99-xqsk5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:06:58Z"
      message: 'network-check-target-ip-10-0-140-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.461037ms
      message: 'network-check-target-ip-10-0-140-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:48:58Z"
    - latency: 2.386417ms
      message: 'network-check-target-ip-10-0-140-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:47:58Z"
    - latency: 2.183688ms
      message: 'network-check-target-ip-10-0-140-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:46:58Z"
    - latency: 2.253931ms
      message: 'network-check-target-ip-10-0-140-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:45:58Z"
    - latency: 14.422456ms
      message: 'network-check-target-ip-10-0-140-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:44:58Z"
    - latency: 2.00222ms
      message: 'network-check-target-ip-10-0-140-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:43:58Z"
    - latency: 2.297345ms
      message: 'network-check-target-ip-10-0-140-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:42:58Z"
    - latency: 2.197421ms
      message: 'network-check-target-ip-10-0-140-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:41:58Z"
    - latency: 2.386127ms
      message: 'network-check-target-ip-10-0-140-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:40:58Z"
    - latency: 10.584966ms
      message: 'network-check-target-ip-10-0-140-241: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:39:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-04T00:59:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-48-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-48.us-east-2.compute.internal
      uid: 6d1abe52-01b3-45db-bc06-ae1ce4883f26
    resourceVersion: "113989"
    uid: d07d8c85-e69e-4a1e-a67e-7caf666711fe
  spec:
    sourcePod: network-check-source-6f78d59f99-xqsk5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-04T01:05:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.047317ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:47:58Z"
    - latency: 1.759784ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:47:58Z"
    - latency: 1.148448ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:46:58Z"
    - latency: 2.224304ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:46:58Z"
    - latency: 1.186067ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:45:58Z"
    - latency: 2.032641ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:45:58Z"
    - latency: 1.460442ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:44:58Z"
    - latency: 15.712239ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:44:58Z"
    - latency: 1.10288ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-04T01:43:58Z"
    - latency: 1.96631ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-04T01:43:58Z"
kind: List
metadata:
  resourceVersion: ""