Comment # 29 on bug 1046436 from Thomas Blume

(In reply to Lukas Ocilka from comment #26)
> OK, so we have basically two options:
> 
> A. In the installer, write /etc/vconsole.conf directly, as there's no
>    systemd running and thus we can't use it.
> 
> B. Create yet another one-off systemd service (script) that would
>    be called during the system boot and adjust all settings that
>    can't be set during the initial installation. The service and the
>    script would not be part of YaST but part of some separate package
>    as no "YaST on the system" is a required feature. Moreover, it would
>    have to be called before YaST.Firstboot, which actually allows
>    adjusting the system via YaST UI and also before YaST.Second-Stage,
>    which is optional for AutoYaST (and which can also change the system)
> 
> Both options are somewhere between "the solution" and "a hack"...

C. Extend systemd-firstboot to cover kbd settings.
   The systemd-firstboot manpage states:
-->
Note that this tool operates directly on the file system and does not involve
any running system services, unlike localectl(1), timedatectl(1) or
hostnamectl(1). This allows systemd-firstboot to operate on mounted but not
booted disk images and in early boot.
--<

systemd-firstboot is available in the installation system, so this is the tool
we would need.
Still, implementation of kbd setting support might take a while and upstream
acceptance is not guaranteed.