apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:24:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-11-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-11.ec2.internal
      uid: 8a920546-51e1-40d6-bdd5-93af25326e8b
    resourceVersion: "54737"
    uid: 81c7c08d-fa04-4e70-b783-3bb49b24d851
  spec:
    sourcePod: network-check-source-989f8b8dc-n6skq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:31:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.612µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:59:36Z"
    - latency: 910.441µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:36Z"
    - latency: 1.132847ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:36Z"
    - latency: 1.408843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:36Z"
    - latency: 730.061µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:55:36Z"
    - latency: 1.255385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:54:36Z"
    - latency: 953.075µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:53:36Z"
    - latency: 1.076774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:52:36Z"
    - latency: 1.012713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:51:36Z"
    - latency: 1.10176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:50:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:24:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-11-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-11.ec2.internal
      uid: 8a920546-51e1-40d6-bdd5-93af25326e8b
    resourceVersion: "55865"
    uid: ad3d9424-22f7-418e-83f7-5af0c25e0117
  spec:
    sourcePod: network-check-source-989f8b8dc-n6skq
    targetEndpoint: a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:30:36Z"
      message: 'load-balancer-api-external: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.559603ms
      message: 'load-balancer-api-external: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:00:36Z"
    - latency: 6.748299ms
      message: 'load-balancer-api-external: resolved host name a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:00:36Z"
    - latency: 5.400105ms
      message: 'load-balancer-api-external: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:59:36Z"
    - latency: 6.777207ms
      message: 'load-balancer-api-external: resolved host name a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:59:36Z"
    - latency: 3.714865ms
      message: 'load-balancer-api-external: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:36Z"
    - latency: 5.977336ms
      message: 'load-balancer-api-external: resolved host name a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:58:36Z"
    - latency: 4.452123ms
      message: 'load-balancer-api-external: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:36Z"
    - latency: 7.582748ms
      message: 'load-balancer-api-external: resolved host name a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:57:36Z"
    - latency: 3.567937ms
      message: 'load-balancer-api-external: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:36Z"
    - latency: 8.414614ms
      message: 'load-balancer-api-external: resolved host name a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:56:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:24:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-11-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-11.ec2.internal
      uid: 8a920546-51e1-40d6-bdd5-93af25326e8b
    resourceVersion: "55867"
    uid: 1b899e23-26a1-4551-9b2c-3c55e9498e7a
  spec:
    sourcePod: network-check-source-989f8b8dc-n6skq
    targetEndpoint: a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:30:36Z"
      message: 'load-balancer-api-internal: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.398323ms
      message: 'load-balancer-api-internal: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:00:36Z"
    - latency: 6.719792ms
      message: 'load-balancer-api-internal: resolved host name a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:00:36Z"
    - latency: 5.431936ms
      message: 'load-balancer-api-internal: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:59:36Z"
    - latency: 6.760481ms
      message: 'load-balancer-api-internal: resolved host name a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:59:36Z"
    - latency: 3.753531ms
      message: 'load-balancer-api-internal: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:36Z"
    - latency: 6.121915ms
      message: 'load-balancer-api-internal: resolved host name a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:58:36Z"
    - latency: 5.098287ms
      message: 'load-balancer-api-internal: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:36Z"
    - latency: 7.644492ms
      message: 'load-balancer-api-internal: resolved host name a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:57:36Z"
    - latency: 3.635551ms
      message: 'load-balancer-api-internal: tcp connection to a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:36Z"
    - latency: 8.500801ms
      message: 'load-balancer-api-internal: resolved host name a291fe7f076784bdd8569794114815ac-50068c96626942f8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:56:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:24:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-11-to-network-check-target-ip-10-0-128-90
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-11.ec2.internal
      uid: 8a920546-51e1-40d6-bdd5-93af25326e8b
    resourceVersion: "54736"
    uid: e9de7ef8-b180-49d7-a336-c58fb45c4548
  spec:
    sourcePod: network-check-source-989f8b8dc-n6skq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:31:36Z"
      message: 'network-check-target-ip-10-0-128-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.194176ms
      message: 'network-check-target-ip-10-0-128-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:59:36Z"
    - latency: 2.249446ms
      message: 'network-check-target-ip-10-0-128-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:36Z"
    - latency: 2.48421ms
      message: 'network-check-target-ip-10-0-128-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:36Z"
    - latency: 2.752945ms
      message: 'network-check-target-ip-10-0-128-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:36Z"
    - latency: 2.133075ms
      message: 'network-check-target-ip-10-0-128-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:55:36Z"
    - latency: 2.538325ms
      message: 'network-check-target-ip-10-0-128-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:54:36Z"
    - latency: 2.253382ms
      message: 'network-check-target-ip-10-0-128-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:53:36Z"
    - latency: 2.385955ms
      message: 'network-check-target-ip-10-0-128-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:52:36Z"
    - latency: 2.552526ms
      message: 'network-check-target-ip-10-0-128-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:51:36Z"
    - latency: 2.338136ms
      message: 'network-check-target-ip-10-0-128-90: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:50:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:24:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-11-to-network-check-target-ip-10-0-131-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-11.ec2.internal
      uid: 8a920546-51e1-40d6-bdd5-93af25326e8b
    resourceVersion: "54734"
    uid: ca8b3e88-1383-4b56-89e1-79501eea9237
  spec:
    sourcePod: network-check-source-989f8b8dc-n6skq
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:31:36Z"
      message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.144408ms
      message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:59:36Z"
    - latency: 2.323647ms
      message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:36Z"
    - latency: 2.066785ms
      message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:36Z"
    - latency: 2.133969ms
      message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:36Z"
    - latency: 2.639253ms
      message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:55:36Z"
    - latency: 2.206774ms
      message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:54:36Z"
    - latency: 2.538373ms
      message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:53:36Z"
    - latency: 2.165418ms
      message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:52:36Z"
    - latency: 2.53356ms
      message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:51:36Z"
    - latency: 2.2145ms
      message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:50:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:24:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-11-to-network-check-target-ip-10-0-133-11
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-11.ec2.internal
      uid: 8a920546-51e1-40d6-bdd5-93af25326e8b
    resourceVersion: "54735"
    uid: df347764-127d-409c-8df8-269eafed208d
  spec:
    sourcePod: network-check-source-989f8b8dc-n6skq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:31:36Z"
      message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.190224ms
      message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:59:36Z"
    - latency: 977.249µs
      message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:36Z"
    - latency: 1.206782ms
      message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:36Z"
    - latency: 772.231µs
      message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:36Z"
    - latency: 811.347µs
      message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:55:36Z"
    - latency: 911.889µs
      message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:54:36Z"
    - latency: 959.353µs
      message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:53:36Z"
    - latency: 930.762µs
      message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:52:36Z"
    - latency: 1.145008ms
      message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:51:36Z"
    - latency: 1.324691ms
      message: 'network-check-target-ip-10-0-133-11: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:50:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:24:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-11-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-11.ec2.internal
      uid: 8a920546-51e1-40d6-bdd5-93af25326e8b
    resourceVersion: "55864"
    uid: d84a48cb-5dec-4bc9-8c37-29315dcecb7e
  spec:
    sourcePod: network-check-source-989f8b8dc-n6skq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:30:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 892.555µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T22:00:36Z"
    - latency: 1.737192ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T22:00:36Z"
    - latency: 1.150998ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:59:36Z"
    - latency: 2.138264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:59:36Z"
    - latency: 773.73µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:36Z"
    - latency: 1.697382ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:58:36Z"
    - latency: 834.061µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:36Z"
    - latency: 1.930858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:57:36Z"
    - latency: 713.638µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:36Z"
    - latency: 1.637412ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:56:36Z"
kind: List
metadata:
  resourceVersion: ""