apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:05:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-197-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-197.us-west-1.compute.internal
      uid: 33060f6d-f1a4-4c70-b24c-bf0309dcedd8
    resourceVersion: "110282"
    uid: 57697423-3efd-4178-b844-4d22caca8146
  spec:
    sourcePod: network-check-source-6f78d59f99-bpmjc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:12:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.468117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:08:22Z"
    - latency: 1.129098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:07:22Z"
    - latency: 1.53746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:06:22Z"
    - latency: 1.499076ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:05:22Z"
    - latency: 1.000919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:04:22Z"
    - latency: 1.845788ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:03:22Z"
    - latency: 984.66µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:02:22Z"
    - latency: 1.458701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:01:22Z"
    - latency: 1.521938ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:00:22Z"
    - latency: 1.050026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:59:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:05:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-197-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-197.us-west-1.compute.internal
      uid: 33060f6d-f1a4-4c70-b24c-bf0309dcedd8
    resourceVersion: "116502"
    uid: 622ccce1-6ed2-4047-b4ae-0832cbb95c6c
  spec:
    sourcePod: network-check-source-6f78d59f99-bpmjc
    targetEndpoint: a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:11:23Z"
      message: 'load-balancer-api-external: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.388562623s
      message: 'load-balancer-api-external: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:11:23Z"
    - latency: 6.640675ms
      message: 'load-balancer-api-external: resolved host name a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:11:22Z"
    - latency: 53.663242ms
      message: 'load-balancer-api-external: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:10:23Z"
    - latency: 6.671338ms
      message: 'load-balancer-api-external: resolved host name a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:10:22Z"
    - latency: 56.116478ms
      message: 'load-balancer-api-external: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:09:23Z"
    - latency: 6.573743ms
      message: 'load-balancer-api-external: resolved host name a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:09:22Z"
    - latency: 54.83761ms
      message: 'load-balancer-api-external: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:08:23Z"
    - latency: 7.329907ms
      message: 'load-balancer-api-external: resolved host name a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:08:22Z"
    - latency: 53.999732ms
      message: 'load-balancer-api-external: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:07:23Z"
    - latency: 6.809168ms
      message: 'load-balancer-api-external: resolved host name a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:07:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:05:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-197-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-197.us-west-1.compute.internal
      uid: 33060f6d-f1a4-4c70-b24c-bf0309dcedd8
    resourceVersion: "116363"
    uid: 7bffb5b4-7fa1-4537-bfa8-b8d6c44485c5
  spec:
    sourcePod: network-check-source-6f78d59f99-bpmjc
    targetEndpoint: a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:11:23Z"
      message: 'load-balancer-api-internal: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.798237ms
      message: 'load-balancer-api-internal: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:11:23Z"
    - latency: 6.710649ms
      message: 'load-balancer-api-internal: resolved host name a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:11:22Z"
    - latency: 3.387974079s
      message: 'load-balancer-api-internal: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:10:23Z"
    - latency: 6.729812ms
      message: 'load-balancer-api-internal: resolved host name a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:10:22Z"
    - latency: 64.616514ms
      message: 'load-balancer-api-internal: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:09:23Z"
    - latency: 6.63765ms
      message: 'load-balancer-api-internal: resolved host name a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:09:22Z"
    - latency: 54.846082ms
      message: 'load-balancer-api-internal: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:08:23Z"
    - latency: 7.383177ms
      message: 'load-balancer-api-internal: resolved host name a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:08:22Z"
    - latency: 53.990954ms
      message: 'load-balancer-api-internal: tcp connection to a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:07:23Z"
    - latency: 6.782731ms
      message: 'load-balancer-api-internal: resolved host name a53752eb2738248268d838fbfc908485-8edbb764ce6e4113.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:07:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:05:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-197-to-network-check-target-ip-10-0-133-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-197.us-west-1.compute.internal
      uid: 33060f6d-f1a4-4c70-b24c-bf0309dcedd8
    resourceVersion: "110089"
    uid: ba13b9e4-42a8-4448-810f-e21a88ed6754
  spec:
    sourcePod: network-check-source-6f78d59f99-bpmjc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:12:22Z"
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.686721ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:08:22Z"
    - latency: 1.076645ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:07:22Z"
    - latency: 1.126342ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:06:22Z"
    - latency: 1.004057ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:05:22Z"
    - latency: 1.073629ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:04:22Z"
    - latency: 1.167273ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:03:22Z"
    - latency: 1.162731ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:02:22Z"
    - latency: 1.026237ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:01:22Z"
    - latency: 1.375152ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:00:22Z"
    - latency: 1.612203ms
      message: 'network-check-target-ip-10-0-133-197: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:59:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:05:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-197-to-network-check-target-ip-10-0-140-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-197.us-west-1.compute.internal
      uid: 33060f6d-f1a4-4c70-b24c-bf0309dcedd8
    resourceVersion: "110091"
    uid: 2a5d1d57-6253-4bcc-9c76-1692610090d8
  spec:
    sourcePod: network-check-source-6f78d59f99-bpmjc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:12:23Z"
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.279739ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:08:22Z"
    - latency: 2.036744ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:07:22Z"
    - latency: 2.084097ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:06:22Z"
    - latency: 2.430894ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:05:22Z"
    - latency: 2.918961ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:04:22Z"
    - latency: 2.609264ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:03:22Z"
    - latency: 2.05928ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:02:22Z"
    - latency: 2.727372ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:01:22Z"
    - latency: 2.356678ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:00:22Z"
    - latency: 2.307651ms
      message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:59:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:05:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-197-to-network-check-target-ip-10-0-141-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-197.us-west-1.compute.internal
      uid: 33060f6d-f1a4-4c70-b24c-bf0309dcedd8
    resourceVersion: "110090"
    uid: 8277584c-3d8b-4529-bc21-587669e1a408
  spec:
    sourcePod: network-check-source-6f78d59f99-bpmjc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:12:23Z"
      message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.456087ms
      message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:08:22Z"
    - latency: 2.206654ms
      message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:07:22Z"
    - latency: 2.200137ms
      message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:06:22Z"
    - latency: 2.188344ms
      message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:05:22Z"
    - latency: 2.592176ms
      message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:04:22Z"
    - latency: 2.737964ms
      message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:03:22Z"
    - latency: 2.384712ms
      message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:02:22Z"
    - latency: 2.681486ms
      message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:01:22Z"
    - latency: 2.464962ms
      message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:00:22Z"
    - latency: 2.700661ms
      message: 'network-check-target-ip-10-0-141-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:59:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T01:05:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-197-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-197.us-west-1.compute.internal
      uid: 33060f6d-f1a4-4c70-b24c-bf0309dcedd8
    resourceVersion: "116364"
    uid: a789863d-fe61-414f-b2bd-f07ed52d813b
  spec:
    sourcePod: network-check-source-6f78d59f99-bpmjc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T01:11:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.107143ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:11:23Z"
    - latency: 918.814µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:11:23Z"
    - latency: 1.061037ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:10:23Z"
    - latency: 928.147µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:10:23Z"
    - latency: 1.596047ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:09:23Z"
    - latency: 724.945µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:09:23Z"
    - latency: 1.119371ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:08:23Z"
    - latency: 1.227606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:08:23Z"
    - latency: 907.123µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T02:07:23Z"
    - latency: 598.516µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T02:07:23Z"
kind: List
metadata:
  resourceVersion: ""