Option to connect to hosts using password authntication from RKE?

[shivakumar5]

RKE version:
2.7.9
Docker version: (docker version,docker info preferred)
23.0.6
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
NAME="Red Hat Enterprise Linux Server"
VERSION="7.9 (Maipo)"
ID="rhel"

kennel: 3.10.0-1160.81.1.el7.x86_64

Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
VirtualBox

cluster.yml file:

#Ansible managed

kubernetes_version: v1.26.11-rancher2-2

nodes:
  - address: "some-ip"
    user: "username"
    role: [etcd,controlplane,worker]


services:
  etcd:
    snapshot: true
    creation: 6h
    retention: 24h
    backup_config:
      enabled: true
      interval_hours: 12
      retention: 6
  kubelet:
    generate_serving_certificate: true
    extra_args:
      protect-kernel-defaults: true
  kube-api:
    secrets_encryption_config:
      enabled: true

private_registries:
- url: registry.example.com/dockerhub-proxy
  is_default: true

ingress:
  provider: nginx
  network_mode: hostPort
  http_port: 80
  https_port: 443

addons: |-
    ---
    apiVersion: v1
    kind: ConfigMap
    metadata:
      name: custom-headers
      namespace: ingress-nginx
    data:
      X-Content-Type-Options: "nosniff"
      X-Frame-Options: "SAMEORIGIN always"
      X-XSS-Protection: "1; mode=block"

Steps to Reproduce:
I'm creating the rancher cluster using ansible. The ansible connects to VMs using Username and Password.
But while running rke up command I'm getting error as

Failed to set up SSH tunneling for host []: Can't establish dialer connection: Error while reading SSH key file: open .ssh/id_rsa: no such file or directory.

I don't want to connect through ssh keys, I want to connect using username and password.

is there any option for that?

Results:

[github-actions]

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.