apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:22:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-29-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-29.us-west-1.compute.internal
      uid: 6637dd13-0348-4d2e-b60a-e8ee34765c1e
    resourceVersion: "108978"
    uid: 7e50d5da-e09d-461b-ba70-bed0cfeefac4
  spec:
    sourcePod: network-check-source-6f78d59f99-fbzx6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:29:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 860.014µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:31Z"
    - latency: 826.511µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:31Z"
    - latency: 878.221µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:30:31Z"
    - latency: 773.984µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:29:31Z"
    - latency: 853.242µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:28:31Z"
    - latency: 1.21536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:27:31Z"
    - latency: 833.221µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:26:31Z"
    - latency: 838.343µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:25:31Z"
    - latency: 894.844µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:24:31Z"
    - latency: 1.258875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:23:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:22:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-29-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-29.us-west-1.compute.internal
      uid: 6637dd13-0348-4d2e-b60a-e8ee34765c1e
    resourceVersion: "106036"
    uid: 5e7d3b88-dfe6-4882-a71e-16bff32cf9e1
  spec:
    sourcePod: network-check-source-6f78d59f99-fbzx6
    targetEndpoint: ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:28:32Z"
      message: 'load-balancer-api-external: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.629546ms
      message: 'load-balancer-api-external: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:28:31Z"
    - latency: 6.511141ms
      message: 'load-balancer-api-external: resolved host name ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:28:31Z"
    - latency: 53.428639ms
      message: 'load-balancer-api-external: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:27:31Z"
    - latency: 6.682046ms
      message: 'load-balancer-api-external: resolved host name ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:27:31Z"
    - latency: 54.001206ms
      message: 'load-balancer-api-external: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:26:31Z"
    - latency: 6.93107ms
      message: 'load-balancer-api-external: resolved host name ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:26:31Z"
    - latency: 53.468928ms
      message: 'load-balancer-api-external: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:25:31Z"
    - latency: 6.652969ms
      message: 'load-balancer-api-external: resolved host name ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:25:31Z"
    - latency: 53.998289ms
      message: 'load-balancer-api-external: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:24:31Z"
    - latency: 6.602789ms
      message: 'load-balancer-api-external: resolved host name ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:24:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:22:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-29-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-29.us-west-1.compute.internal
      uid: 6637dd13-0348-4d2e-b60a-e8ee34765c1e
    resourceVersion: "106035"
    uid: 9908e097-9965-4577-8666-6232ef9d4921
  spec:
    sourcePod: network-check-source-6f78d59f99-fbzx6
    targetEndpoint: ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:28:32Z"
      message: 'load-balancer-api-internal: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.498902ms
      message: 'load-balancer-api-internal: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:28:31Z"
    - latency: 6.610685ms
      message: 'load-balancer-api-internal: resolved host name ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:28:31Z"
    - latency: 53.411054ms
      message: 'load-balancer-api-internal: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:27:31Z"
    - latency: 6.639977ms
      message: 'load-balancer-api-internal: resolved host name ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:27:31Z"
    - latency: 54.040435ms
      message: 'load-balancer-api-internal: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:26:31Z"
    - latency: 7.012047ms
      message: 'load-balancer-api-internal: resolved host name ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:26:31Z"
    - latency: 53.271456ms
      message: 'load-balancer-api-internal: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:25:31Z"
    - latency: 6.60245ms
      message: 'load-balancer-api-internal: resolved host name ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:25:31Z"
    - latency: 53.956174ms
      message: 'load-balancer-api-internal: tcp connection to ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:24:31Z"
    - latency: 6.519619ms
      message: 'load-balancer-api-internal: resolved host name ab4a4e8a057d64e13b2573a04657ce20-dcfeed6681acbb51.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:24:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:22:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-29-to-network-check-target-ip-10-0-130-195
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-29.us-west-1.compute.internal
      uid: 6637dd13-0348-4d2e-b60a-e8ee34765c1e
    resourceVersion: "108974"
    uid: 3d95b7fb-d865-41f4-bb89-8c956ce5a177
  spec:
    sourcePod: network-check-source-6f78d59f99-fbzx6
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:29:31Z"
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.337889ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:31Z"
    - latency: 1.976868ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:31Z"
    - latency: 2.162144ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:30:31Z"
    - latency: 2.278423ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:29:31Z"
    - latency: 2.346091ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:28:31Z"
    - latency: 2.205597ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:27:31Z"
    - latency: 1.850528ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:26:31Z"
    - latency: 2.025948ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:25:31Z"
    - latency: 2.12795ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:24:31Z"
    - latency: 2.445496ms
      message: 'network-check-target-ip-10-0-130-195: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:23:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:22:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-29-to-network-check-target-ip-10-0-138-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-29.us-west-1.compute.internal
      uid: 6637dd13-0348-4d2e-b60a-e8ee34765c1e
    resourceVersion: "108976"
    uid: 5f966c0d-61c5-4aff-8f9f-60eebb11b22b
  spec:
    sourcePod: network-check-source-6f78d59f99-fbzx6
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:29:31Z"
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.275882ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:31Z"
    - latency: 2.087203ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:31Z"
    - latency: 1.967167ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:30:31Z"
    - latency: 2.263976ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:29:31Z"
    - latency: 2.179951ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:28:31Z"
    - latency: 1.85775ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:27:31Z"
    - latency: 2.221469ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:26:31Z"
    - latency: 2.163548ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:25:31Z"
    - latency: 2.185948ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:24:31Z"
    - latency: 2.375078ms
      message: 'network-check-target-ip-10-0-138-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:23:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:22:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-29-to-network-check-target-ip-10-0-141-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-29.us-west-1.compute.internal
      uid: 6637dd13-0348-4d2e-b60a-e8ee34765c1e
    resourceVersion: "108973"
    uid: 7a0a466c-2258-42d1-867a-b45335eeb598
  spec:
    sourcePod: network-check-source-6f78d59f99-fbzx6
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:29:31Z"
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.018959ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:32:31Z"
    - latency: 1.184289ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:31:31Z"
    - latency: 1.303601ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:30:31Z"
    - latency: 1.190112ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:29:31Z"
    - latency: 934.462µs
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:28:31Z"
    - latency: 1.34431ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:27:31Z"
    - latency: 1.482894ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:26:31Z"
    - latency: 890.399µs
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:25:31Z"
    - latency: 1.649169ms
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:24:31Z"
    - latency: 868.529µs
      message: 'network-check-target-ip-10-0-141-29: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:23:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:22:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-29-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-29.us-west-1.compute.internal
      uid: 6637dd13-0348-4d2e-b60a-e8ee34765c1e
    resourceVersion: "106031"
    uid: 30fbb884-27fd-4034-b79a-73e6418325c4
  spec:
    sourcePod: network-check-source-6f78d59f99-fbzx6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:28:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.24103ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:28:31Z"
    - latency: 1.786617ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:28:31Z"
    - latency: 830.727µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:27:31Z"
    - latency: 1.747886ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:27:31Z"
    - latency: 1.126072ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:26:31Z"
    - latency: 1.715473ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:26:31Z"
    - latency: 1.388523ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:25:31Z"
    - latency: 1.887522ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:25:31Z"
    - latency: 1.221073ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:24:31Z"
    - latency: 1.715113ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:24:31Z"
kind: List
metadata:
  resourceVersion: ""