apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-188-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-188.ec2.internal
      uid: 8086e88c-8a41-4551-bc59-b815a49762b6
    resourceVersion: "56530"
    uid: 0aed8f7b-a04c-4283-bf48-baaa05cf6ce4
  spec:
    sourcePod: network-check-source-6f8b768455-b66mm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:01:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 975.643µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:20Z"
    - latency: 892.329µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:21:20Z"
    - latency: 1.009778ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:20:20Z"
    - latency: 839.413µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:19:20Z"
    - latency: 1.096928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:18:20Z"
    - latency: 1.128848ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:17:20Z"
    - latency: 1.02507ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:16:20Z"
    - latency: 1.061606ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:15:20Z"
    - latency: 1.115003ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:14:20Z"
    - latency: 1.143094ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:13:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-188-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-188.ec2.internal
      uid: 8086e88c-8a41-4551-bc59-b815a49762b6
    resourceVersion: "58320"
    uid: be09528d-8cc7-4d8e-af2b-9ade6f34e244
  spec:
    sourcePod: network-check-source-6f8b768455-b66mm
    targetEndpoint: aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:00:20Z"
      message: 'load-balancer-api-external: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.767721ms
      message: 'load-balancer-api-external: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:24:20Z"
    - latency: 7.488156ms
      message: 'load-balancer-api-external: resolved host name aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:24:20Z"
    - latency: 5.294646ms
      message: 'load-balancer-api-external: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:23:20Z"
    - latency: 7.347375ms
      message: 'load-balancer-api-external: resolved host name aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:23:20Z"
    - latency: 2.96687ms
      message: 'load-balancer-api-external: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:20Z"
    - latency: 7.812124ms
      message: 'load-balancer-api-external: resolved host name aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:22:20Z"
    - latency: 4.326899ms
      message: 'load-balancer-api-external: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:21:20Z"
    - latency: 6.496239ms
      message: 'load-balancer-api-external: resolved host name aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:21:20Z"
    - latency: 4.727901ms
      message: 'load-balancer-api-external: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:20:20Z"
    - latency: 7.332768ms
      message: 'load-balancer-api-external: resolved host name aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:20:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-188-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-188.ec2.internal
      uid: 8086e88c-8a41-4551-bc59-b815a49762b6
    resourceVersion: "58319"
    uid: 8d84dea0-277d-435a-abdc-230c8118fea7
  spec:
    sourcePod: network-check-source-6f8b768455-b66mm
    targetEndpoint: aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:00:20Z"
      message: 'load-balancer-api-internal: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.760196ms
      message: 'load-balancer-api-internal: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:24:20Z"
    - latency: 7.40032ms
      message: 'load-balancer-api-internal: resolved host name aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:24:20Z"
    - latency: 5.269814ms
      message: 'load-balancer-api-internal: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:23:20Z"
    - latency: 7.322169ms
      message: 'load-balancer-api-internal: resolved host name aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:23:20Z"
    - latency: 2.840142ms
      message: 'load-balancer-api-internal: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:20Z"
    - latency: 7.791198ms
      message: 'load-balancer-api-internal: resolved host name aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:22:20Z"
    - latency: 4.517543ms
      message: 'load-balancer-api-internal: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:21:20Z"
    - latency: 6.471379ms
      message: 'load-balancer-api-internal: resolved host name aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:21:20Z"
    - latency: 4.39716ms
      message: 'load-balancer-api-internal: tcp connection to aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:20:20Z"
    - latency: 7.299608ms
      message: 'load-balancer-api-internal: resolved host name aaa5583ab7e8a483086b18ea06081fba-b9e6138735160016.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:20:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-188-to-network-check-target-ip-10-0-129-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-188.ec2.internal
      uid: 8086e88c-8a41-4551-bc59-b815a49762b6
    resourceVersion: "56529"
    uid: 4f19cb1d-3b1f-428b-8293-7acf2466de3c
  spec:
    sourcePod: network-check-source-6f8b768455-b66mm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:01:20Z"
      message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.633469ms
      message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:20Z"
    - latency: 2.029886ms
      message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:21:20Z"
    - latency: 2.485458ms
      message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:20:20Z"
    - latency: 2.477641ms
      message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:19:20Z"
    - latency: 2.412268ms
      message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:18:20Z"
    - latency: 2.593644ms
      message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:17:20Z"
    - latency: 2.819741ms
      message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:16:20Z"
    - latency: 2.866272ms
      message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:15:20Z"
    - latency: 2.6326ms
      message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:14:20Z"
    - latency: 1.904612ms
      message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:13:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-188-to-network-check-target-ip-10-0-133-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-188.ec2.internal
      uid: 8086e88c-8a41-4551-bc59-b815a49762b6
    resourceVersion: "56527"
    uid: 29a89b7a-6cf7-45e1-a46d-427784ac1aef
  spec:
    sourcePod: network-check-source-6f8b768455-b66mm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:01:20Z"
      message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.06306ms
      message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:20Z"
    - latency: 926.174µs
      message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:21:20Z"
    - latency: 831.931µs
      message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:20:20Z"
    - latency: 971.39µs
      message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:19:20Z"
    - latency: 988.191µs
      message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:18:20Z"
    - latency: 922.978µs
      message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:17:20Z"
    - latency: 976.062µs
      message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:16:20Z"
    - latency: 1.05519ms
      message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:15:20Z"
    - latency: 939.75µs
      message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:14:20Z"
    - latency: 1.838902ms
      message: 'network-check-target-ip-10-0-133-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:13:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-188-to-network-check-target-ip-10-0-141-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-188.ec2.internal
      uid: 8086e88c-8a41-4551-bc59-b815a49762b6
    resourceVersion: "56528"
    uid: 528f84fc-8eaa-4f93-83f4-e9646b5ead0d
  spec:
    sourcePod: network-check-source-6f8b768455-b66mm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:01:20Z"
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.412837ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:20Z"
    - latency: 2.18721ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:21:20Z"
    - latency: 2.030654ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:20:20Z"
    - latency: 2.321753ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:19:20Z"
    - latency: 2.632373ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:18:20Z"
    - latency: 2.412895ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:17:20Z"
    - latency: 2.398308ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:16:20Z"
    - latency: 2.087202ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:15:20Z"
    - latency: 2.253732ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:14:20Z"
    - latency: 2.258136ms
      message: 'network-check-target-ip-10-0-141-180: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:13:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T02:54:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-188-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-188.ec2.internal
      uid: 8086e88c-8a41-4551-bc59-b815a49762b6
    resourceVersion: "58318"
    uid: 76fc34d5-751e-477f-9e32-e3d17b67ba7e
  spec:
    sourcePod: network-check-source-6f8b768455-b66mm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T03:00:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.069513ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:24:20Z"
    - latency: 2.051255ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:24:20Z"
    - latency: 921.783µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:23:20Z"
    - latency: 1.773745ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:23:20Z"
    - latency: 1.065684ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:22:20Z"
    - latency: 2.033079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:22:20Z"
    - latency: 712.765µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:21:20Z"
    - latency: 1.931516ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:21:20Z"
    - latency: 1.183897ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T03:20:20Z"
    - latency: 2.307169ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T03:20:20Z"
kind: List
metadata:
  resourceVersion: ""