apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:22:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: fcaece8c-003f-49d6-953b-e84110cc5f5c
    resourceVersion: "54429"
    uid: 4b3e7986-4920-4e19-846e-4503ae51b17b
  spec:
    sourcePod: network-check-source-685456655f-gqclh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:29:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.101024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:50:07Z"
    - latency: 1.595959ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:49:07Z"
    - latency: 937.499µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:48:07Z"
    - latency: 1.314937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:47:07Z"
    - latency: 1.201898ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:46:07Z"
    - latency: 1.427766ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:45:07Z"
    - latency: 1.208742ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:44:07Z"
    - latency: 1.204937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:43:07Z"
    - latency: 1.564919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:42:07Z"
    - latency: 1.129356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:41:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:22:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: fcaece8c-003f-49d6-953b-e84110cc5f5c
    resourceVersion: "56756"
    uid: 9d6a9db2-f9cb-4807-8ba8-d74012dc6c52
  spec:
    sourcePod: network-check-source-685456655f-gqclh
    targetEndpoint: a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:28:07Z"
      message: 'load-balancer-api-external: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.490939ms
      message: 'load-balancer-api-external: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:52:07Z"
    - latency: 6.743169ms
      message: 'load-balancer-api-external: resolved host name a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:52:07Z"
    - latency: 5.374268ms
      message: 'load-balancer-api-external: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:51:07Z"
    - latency: 7.254609ms
      message: 'load-balancer-api-external: resolved host name a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:51:07Z"
    - latency: 5.120929ms
      message: 'load-balancer-api-external: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:50:07Z"
    - latency: 6.215921ms
      message: 'load-balancer-api-external: resolved host name a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:50:07Z"
    - latency: 4.326605ms
      message: 'load-balancer-api-external: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:49:07Z"
    - latency: 7.032676ms
      message: 'load-balancer-api-external: resolved host name a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:49:07Z"
    - latency: 3.629531ms
      message: 'load-balancer-api-external: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:48:07Z"
    - latency: 7.212199ms
      message: 'load-balancer-api-external: resolved host name a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:48:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:22:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: fcaece8c-003f-49d6-953b-e84110cc5f5c
    resourceVersion: "56755"
    uid: 448e43f8-fca4-44cf-aa47-1325a7eb3008
  spec:
    sourcePod: network-check-source-685456655f-gqclh
    targetEndpoint: a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:28:07Z"
      message: 'load-balancer-api-internal: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.548985ms
      message: 'load-balancer-api-internal: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:52:07Z"
    - latency: 6.660961ms
      message: 'load-balancer-api-internal: resolved host name a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:52:07Z"
    - latency: 4.259295ms
      message: 'load-balancer-api-internal: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:51:07Z"
    - latency: 7.340197ms
      message: 'load-balancer-api-internal: resolved host name a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:51:07Z"
    - latency: 4.262773ms
      message: 'load-balancer-api-internal: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:50:07Z"
    - latency: 6.197145ms
      message: 'load-balancer-api-internal: resolved host name a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:50:07Z"
    - latency: 4.280893ms
      message: 'load-balancer-api-internal: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:49:07Z"
    - latency: 7.046196ms
      message: 'load-balancer-api-internal: resolved host name a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:49:07Z"
    - latency: 3.609667ms
      message: 'load-balancer-api-internal: tcp connection to a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:48:07Z"
    - latency: 7.241765ms
      message: 'load-balancer-api-internal: resolved host name a62d7513587634e408939099eab35de5-0516ac8628ed8fc7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:48:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:22:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-network-check-target-ip-10-0-129-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: fcaece8c-003f-49d6-953b-e84110cc5f5c
    resourceVersion: "54428"
    uid: 049dd4b0-b9d7-4211-bf1f-052afcd8f121
  spec:
    sourcePod: network-check-source-685456655f-gqclh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:29:07Z"
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.999271ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:50:07Z"
    - latency: 1.922687ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:49:07Z"
    - latency: 1.725301ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:48:07Z"
    - latency: 2.038028ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:47:07Z"
    - latency: 1.839965ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:46:07Z"
    - latency: 2.100645ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:45:07Z"
    - latency: 1.999749ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:44:07Z"
    - latency: 2.280415ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:43:07Z"
    - latency: 2.65437ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:42:07Z"
    - latency: 2.296229ms
      message: 'network-check-target-ip-10-0-129-87: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:41:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:22:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-network-check-target-ip-10-0-135-154
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: fcaece8c-003f-49d6-953b-e84110cc5f5c
    resourceVersion: "54427"
    uid: 134e259e-f1f8-4a28-b991-bd26c85c9e81
  spec:
    sourcePod: network-check-source-685456655f-gqclh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:29:07Z"
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 913.547µs
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:50:07Z"
    - latency: 1.000686ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:49:07Z"
    - latency: 1.143549ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:48:07Z"
    - latency: 1.044829ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:47:07Z"
    - latency: 933.767µs
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:46:07Z"
    - latency: 1.375078ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:45:07Z"
    - latency: 1.064741ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:44:07Z"
    - latency: 1.094984ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:43:07Z"
    - latency: 1.088739ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:42:07Z"
    - latency: 1.045006ms
      message: 'network-check-target-ip-10-0-135-154: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:41:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:22:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-network-check-target-ip-10-0-135-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: fcaece8c-003f-49d6-953b-e84110cc5f5c
    resourceVersion: "54426"
    uid: 9cb15aad-912f-4c8b-94c2-76b9f764bffe
  spec:
    sourcePod: network-check-source-685456655f-gqclh
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:29:07Z"
      message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.093006ms
      message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:50:07Z"
    - latency: 2.333579ms
      message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:49:07Z"
    - latency: 2.345244ms
      message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:48:07Z"
    - latency: 2.28552ms
      message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:47:07Z"
    - latency: 2.244944ms
      message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:46:07Z"
    - latency: 2.031713ms
      message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:45:07Z"
    - latency: 2.203711ms
      message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:44:07Z"
    - latency: 2.323369ms
      message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:43:07Z"
    - latency: 2.179788ms
      message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:42:07Z"
    - latency: 2.330291ms
      message: 'network-check-target-ip-10-0-135-242: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:41:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T16:22:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-154-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-154.ec2.internal
      uid: fcaece8c-003f-49d6-953b-e84110cc5f5c
    resourceVersion: "56754"
    uid: e370146e-baef-48d4-9cfa-7ec7a2c26b33
  spec:
    sourcePod: network-check-source-685456655f-gqclh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T16:28:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.086286ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:52:07Z"
    - latency: 1.69089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:52:07Z"
    - latency: 888.794µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:51:07Z"
    - latency: 1.975267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:51:07Z"
    - latency: 844.946µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:50:07Z"
    - latency: 1.634184ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:50:07Z"
    - latency: 1.146454ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:49:07Z"
    - latency: 2.025256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:49:07Z"
    - latency: 921.072µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T16:48:07Z"
    - latency: 1.877196ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T16:48:07Z"
kind: List
metadata:
  resourceVersion: ""