Unable to configure multiple service-account-issuer or service-account-keyfile parameters for apiserver

[jwitko]

Environment:

• Cloud provider or hardware configuration:
  Hardware deployment

• OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
  AlmaLinux 9
  Kernel 5.14.0-70.30.1.el9_0.x86_64

• Version of Ansible (ansible --version):
  2.12

• Version of Python (python --version):
  3.8.10

Kubespray version (commit) (git rev-parse --short HEAD):
2.20.0

Network plugin used:
Cilium

Full inventory with variables (ansible -i inventory/sample/inventory.ini all -m debug -a "var=hostvars[inventory_hostname]"):
Standard inventory. Nothing special to note.

Command used to invoke ansible:
ansible-playbook -i myInventory -b -e @vars/kubespray.yaml upgrade-cluster.yml -t 'master' -l myServer --diff

Output of ansible run:
Ansible run completes without issue

Anything else do we need to know:
I have a requirement to configure AWS EKS pod-identity-webhook in my hardware cluster.
I am currently unable to do this with KubeSpray because the variable kube_kubeadm_apiserver_extra_args is a simple dict which cannot take multiple of the same keys due to the way YAML functions.
This means that there is no ability to do things native to kubernetes config like specify the apiServer parameter --service-account-key-file multiple times or specify the --service-account-issuer parameter multiple times.

[jwitko]

Fixing this may be a little more difficult than I first imagined. Kubespray is templating a KubeAdm clusterConfig file which also takes these values in as a map and throws a warning if we duplicate the keys before applying the kubeadm command and ends up just taking the last key/value pair.

Looks like this related to kubernetes/kubeadm#1601

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.