apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T07:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: bccb173c-4def-4cd8-8b56-df6709336647
    resourceVersion: "36296"
    uid: ca9f865a-2d78-43c0-abde-3e2d00c885dc
  spec:
    sourcePod: network-check-source-8894fc9bd-gnk92
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T08:02:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026755ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:44:34Z"
    - latency: 1.074067ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:43:34Z"
    - latency: 1.438678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:42:34Z"
    - latency: 865.866µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:41:34Z"
    - latency: 1.562873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:40:34Z"
    - latency: 885.335µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:39:34Z"
    - latency: 1.038617ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:38:34Z"
    - latency: 1.024771ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:37:34Z"
    - latency: 1.050422ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:36:34Z"
    - latency: 839.688µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:35:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T07:55:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: bccb173c-4def-4cd8-8b56-df6709336647
    resourceVersion: "38917"
    uid: 366851a1-de1f-46ca-a5ea-41aadf139bd1
  spec:
    sourcePod: network-check-source-8894fc9bd-gnk92
    targetEndpoint: a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T08:01:34Z"
      message: 'load-balancer-api-external: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.138334ms
      message: 'load-balancer-api-external: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:49:34Z"
    - latency: 6.960107ms
      message: 'load-balancer-api-external: resolved host name a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:49:34Z"
    - latency: 4.376296ms
      message: 'load-balancer-api-external: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:48:34Z"
    - latency: 7.710187ms
      message: 'load-balancer-api-external: resolved host name a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:48:34Z"
    - latency: 5.374328ms
      message: 'load-balancer-api-external: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:47:34Z"
    - latency: 8.455755ms
      message: 'load-balancer-api-external: resolved host name a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:47:34Z"
    - latency: 4.312836ms
      message: 'load-balancer-api-external: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:46:34Z"
    - latency: 7.96176ms
      message: 'load-balancer-api-external: resolved host name a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:46:34Z"
    - latency: 4.362407ms
      message: 'load-balancer-api-external: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:45:34Z"
    - latency: 8.490761ms
      message: 'load-balancer-api-external: resolved host name a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:45:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T07:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: bccb173c-4def-4cd8-8b56-df6709336647
    resourceVersion: "38918"
    uid: ef82f822-0a76-4052-8392-e49447141543
  spec:
    sourcePod: network-check-source-8894fc9bd-gnk92
    targetEndpoint: a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T08:01:34Z"
      message: 'load-balancer-api-internal: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.155947ms
      message: 'load-balancer-api-internal: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:49:34Z"
    - latency: 7.014456ms
      message: 'load-balancer-api-internal: resolved host name a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:49:34Z"
    - latency: 4.381208ms
      message: 'load-balancer-api-internal: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:48:34Z"
    - latency: 7.650664ms
      message: 'load-balancer-api-internal: resolved host name a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:48:34Z"
    - latency: 5.372821ms
      message: 'load-balancer-api-internal: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:47:34Z"
    - latency: 8.401434ms
      message: 'load-balancer-api-internal: resolved host name a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:47:34Z"
    - latency: 4.295703ms
      message: 'load-balancer-api-internal: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:46:34Z"
    - latency: 8.019985ms
      message: 'load-balancer-api-internal: resolved host name a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:46:34Z"
    - latency: 4.382857ms
      message: 'load-balancer-api-internal: tcp connection to a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:45:34Z"
    - latency: 8.381196ms
      message: 'load-balancer-api-internal: resolved host name a886eb271f2164ca3b0315877558d7d7-434e5a3a6aed6ccd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:45:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T07:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-network-check-target-ip-10-0-130-28
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: bccb173c-4def-4cd8-8b56-df6709336647
    resourceVersion: "36295"
    uid: 514561bc-64d4-489e-9b43-7cc6dca2a3d8
  spec:
    sourcePod: network-check-source-8894fc9bd-gnk92
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T08:02:34Z"
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.422615ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:44:34Z"
    - latency: 846.858µs
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:43:34Z"
    - latency: 718.092µs
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:42:34Z"
    - latency: 898.309µs
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:41:34Z"
    - latency: 1.159855ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:40:34Z"
    - latency: 949.137µs
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:39:34Z"
    - latency: 934.946µs
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:38:34Z"
    - latency: 749.152µs
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:37:34Z"
    - latency: 876.03µs
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:36:34Z"
    - latency: 1.176055ms
      message: 'network-check-target-ip-10-0-130-28: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:35:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T07:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-network-check-target-ip-10-0-134-176
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: bccb173c-4def-4cd8-8b56-df6709336647
    resourceVersion: "36293"
    uid: 3fe9a82b-e473-49fb-a6c4-bfd90548b48d
  spec:
    sourcePod: network-check-source-8894fc9bd-gnk92
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T08:02:34Z"
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.69127ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:44:34Z"
    - latency: 1.863663ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:43:34Z"
    - latency: 1.769064ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:42:34Z"
    - latency: 1.775515ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:41:34Z"
    - latency: 1.829906ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:40:34Z"
    - latency: 1.894531ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:39:34Z"
    - latency: 1.594436ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:38:34Z"
    - latency: 1.828951ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:37:34Z"
    - latency: 1.845387ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:36:34Z"
    - latency: 1.728675ms
      message: 'network-check-target-ip-10-0-134-176: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:35:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T07:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-network-check-target-ip-10-0-138-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: bccb173c-4def-4cd8-8b56-df6709336647
    resourceVersion: "36294"
    uid: 0b1bcf75-d881-4d99-8693-e2879b9972b8
  spec:
    sourcePod: network-check-source-8894fc9bd-gnk92
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T08:02:34Z"
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.083176ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:44:34Z"
    - latency: 1.967755ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:43:34Z"
    - latency: 1.898896ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:42:34Z"
    - latency: 1.861128ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:41:34Z"
    - latency: 2.019876ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:40:34Z"
    - latency: 2.137797ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:39:34Z"
    - latency: 2.328634ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:38:34Z"
    - latency: 2.392337ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:37:34Z"
    - latency: 2.173173ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:36:34Z"
    - latency: 1.76266ms
      message: 'network-check-target-ip-10-0-138-143: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:35:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-17T07:55:32Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-28-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-28.ec2.internal
      uid: bccb173c-4def-4cd8-8b56-df6709336647
    resourceVersion: "38916"
    uid: 371ff0eb-afbd-420b-9ef2-747b66bd4ea9
  spec:
    sourcePod: network-check-source-8894fc9bd-gnk92
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-17T08:01:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.069421ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:49:34Z"
    - latency: 1.644796ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:49:34Z"
    - latency: 803.671µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:48:34Z"
    - latency: 1.564739ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:48:34Z"
    - latency: 909.604µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:47:34Z"
    - latency: 1.698254ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:47:34Z"
    - latency: 846.422µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:46:34Z"
    - latency: 1.60784ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:46:34Z"
    - latency: 839.112µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-17T08:45:34Z"
    - latency: 2.323766ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-17T08:45:34Z"
kind: List
metadata:
  resourceVersion: ""