apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-105-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-105.ec2.internal
      uid: e86bbb49-99de-45a0-b53f-6601e3fc2507
    resourceVersion: "161003"
    uid: 8a9d9179-585a-4a04-b499-7e5aa3a6c598
  spec:
    sourcePod: network-check-source-6f78d59f99-bhw8w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:58:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.260682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:08:13Z"
    - latency: 839.609µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:07:13Z"
    - latency: 1.309511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:06:13Z"
    - latency: 977.494µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:05:13Z"
    - latency: 703.483µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:04:13Z"
    - latency: 998.31µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:03:13Z"
    - latency: 836.585µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:02:13Z"
    - latency: 943.915µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:01:13Z"
    - latency: 991.484µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:00:13Z"
    - latency: 1.122982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:59:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-105-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-105.ec2.internal
      uid: e86bbb49-99de-45a0-b53f-6601e3fc2507
    resourceVersion: "161536"
    uid: 7f170f3b-2031-44ed-a073-af567cb40add
  spec:
    sourcePod: network-check-source-6f78d59f99-bhw8w
    targetEndpoint: aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:57:13Z"
      message: 'load-balancer-api-external: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.415368ms
      message: 'load-balancer-api-external: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:09:13Z"
    - latency: 6.733435ms
      message: 'load-balancer-api-external: resolved host name aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:09:13Z"
    - latency: 16.874583ms
      message: 'load-balancer-api-external: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:08:13Z"
    - latency: 7.595925ms
      message: 'load-balancer-api-external: resolved host name aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:08:13Z"
    - latency: 15.957532ms
      message: 'load-balancer-api-external: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:07:13Z"
    - latency: 6.652663ms
      message: 'load-balancer-api-external: resolved host name aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:07:13Z"
    - latency: 16.852359ms
      message: 'load-balancer-api-external: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:06:13Z"
    - latency: 6.444752ms
      message: 'load-balancer-api-external: resolved host name aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:06:13Z"
    - latency: 23.711764ms
      message: 'load-balancer-api-external: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:05:13Z"
    - latency: 7.572597ms
      message: 'load-balancer-api-external: resolved host name aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:05:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-105-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-105.ec2.internal
      uid: e86bbb49-99de-45a0-b53f-6601e3fc2507
    resourceVersion: "161535"
    uid: a17dd351-0fb7-48e8-901e-ce2f59dea0f6
  spec:
    sourcePod: network-check-source-6f78d59f99-bhw8w
    targetEndpoint: aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:57:13Z"
      message: 'load-balancer-api-internal: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.193222ms
      message: 'load-balancer-api-internal: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:09:13Z"
    - latency: 6.67105ms
      message: 'load-balancer-api-internal: resolved host name aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:09:13Z"
    - latency: 16.222454ms
      message: 'load-balancer-api-internal: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:08:13Z"
    - latency: 7.571115ms
      message: 'load-balancer-api-internal: resolved host name aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:08:13Z"
    - latency: 16.066725ms
      message: 'load-balancer-api-internal: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:07:13Z"
    - latency: 6.673039ms
      message: 'load-balancer-api-internal: resolved host name aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:07:13Z"
    - latency: 16.842147ms
      message: 'load-balancer-api-internal: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:06:13Z"
    - latency: 6.534757ms
      message: 'load-balancer-api-internal: resolved host name aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:06:13Z"
    - latency: 16.364437ms
      message: 'load-balancer-api-internal: tcp connection to aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:05:13Z"
    - latency: 7.607141ms
      message: 'load-balancer-api-internal: resolved host name aaffb36b377b6429b9eb7d6a716b0696-d5aca0480982002b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:05:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-105-to-network-check-target-ip-10-0-131-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-105.ec2.internal
      uid: e86bbb49-99de-45a0-b53f-6601e3fc2507
    resourceVersion: "161001"
    uid: f895e083-fc82-45f5-8c55-0bcb0290405e
  spec:
    sourcePod: network-check-source-6f78d59f99-bhw8w
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:58:13Z"
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.434438ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:08:13Z"
    - latency: 2.209558ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:07:13Z"
    - latency: 2.252421ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:06:13Z"
    - latency: 2.340505ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:05:13Z"
    - latency: 2.2797ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:04:13Z"
    - latency: 2.1781ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:03:13Z"
    - latency: 2.902466ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:02:13Z"
    - latency: 2.193419ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:01:13Z"
    - latency: 2.618984ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:00:13Z"
    - latency: 2.44461ms
      message: 'network-check-target-ip-10-0-131-200: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:59:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-105-to-network-check-target-ip-10-0-133-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-105.ec2.internal
      uid: e86bbb49-99de-45a0-b53f-6601e3fc2507
    resourceVersion: "161002"
    uid: 67623e6e-b010-4f7a-af14-3dcc5fa4034b
  spec:
    sourcePod: network-check-source-6f78d59f99-bhw8w
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:58:13Z"
      message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.351331ms
      message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:08:13Z"
    - latency: 2.252381ms
      message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:07:13Z"
    - latency: 2.652807ms
      message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:06:13Z"
    - latency: 2.238047ms
      message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:05:13Z"
    - latency: 2.256431ms
      message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:04:13Z"
    - latency: 2.376296ms
      message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:03:13Z"
    - latency: 2.34707ms
      message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:02:13Z"
    - latency: 2.577771ms
      message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:01:13Z"
    - latency: 1.863212ms
      message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:00:13Z"
    - latency: 2.38222ms
      message: 'network-check-target-ip-10-0-133-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:59:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-105-to-network-check-target-ip-10-0-140-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-105.ec2.internal
      uid: e86bbb49-99de-45a0-b53f-6601e3fc2507
    resourceVersion: "161000"
    uid: 2b45a0dc-ff9a-4a3f-88fa-35493177e6e7
  spec:
    sourcePod: network-check-source-6f78d59f99-bhw8w
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:58:13Z"
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.503377ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:08:13Z"
    - latency: 874.627µs
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:07:13Z"
    - latency: 929.998µs
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:06:13Z"
    - latency: 841.85µs
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:05:13Z"
    - latency: 1.111132ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:04:13Z"
    - latency: 886.756µs
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:03:13Z"
    - latency: 774.113µs
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:02:13Z"
    - latency: 864.071µs
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:01:13Z"
    - latency: 1.214276ms
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:00:13Z"
    - latency: 946.021µs
      message: 'network-check-target-ip-10-0-140-105: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T14:59:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T13:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-105-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-105.ec2.internal
      uid: e86bbb49-99de-45a0-b53f-6601e3fc2507
    resourceVersion: "161534"
    uid: c875ae45-f1a4-4493-89c9-74c94eced875
  spec:
    sourcePod: network-check-source-6f78d59f99-bhw8w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:57:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 852.888µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:09:13Z"
    - latency: 1.713922ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:09:13Z"
    - latency: 1.546666ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:08:13Z"
    - latency: 1.734089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:08:13Z"
    - latency: 1.419764ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:07:13Z"
    - latency: 1.612764ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:07:13Z"
    - latency: 1.123748ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:06:13Z"
    - latency: 1.865301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:06:13Z"
    - latency: 997.631µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T15:05:13Z"
    - latency: 1.804945ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T15:05:13Z"
kind: List
metadata:
  resourceVersion: ""