# Mounting extra k8 volumes in Ansible 17.1

**URL:** <https://forum.ansible.com/t/mounting-extra-k8-volumes-in-ansible-17-1/34997>\
**Category:** AWX Project\
**Tags:** awx, ee\
**Created:** [April 16, 2021, 2:37am UTC](https://forum.ansible.com/t/mounting-extra-k8-volumes-in-ansible-17-1/34997 "2021-04-16T02:37:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brandon\_Ellis](https://avatars.discourse-cdn.com/v4/letter/b/dec6dc/32.png) [@Brandon\_Ellis](https://forum.ansible.com/u/Brandon_Ellis)\
**Post date:** [April 16, 2021, 2:37am UTC](https://forum.ansible.com/t/mounting-extra-k8-volumes-in-ansible-17-1/34997/1 "2021-04-16T02:37:24Z")

</div>

Since AWX seems to be [currently breaking everything](https://github.com/ansible/awx/issues/9863) with EE’s, I thought I might try sticking with version 17.1.

Problem is, I still need to configure volume mounts for files like krb5.conf, logo-login.svg, etc and use LoadBalancer ingresses with SSL support

[I can’t use the operator because I can only use version 0.6 of the operator to deploy AWX 17.1](https://github.com/ansible/awx-operator/issues/139), and of course it doesn’t support LoadBalancer Ingress

So this brings me back to using the Ansible Playbook install method to install 17.1 on a k8 cluster. This doesn’t have native support for any extra volume mounts or LoadBalancer SSL.

How can I hack the AWX install playbook to modify the kubeconfig? What files control volume mounts and Ingress types?

---

<div class="post-metadata">

**Author:** ![Brandon\_Ellis](https://avatars.discourse-cdn.com/v4/letter/b/dec6dc/32.png) [@Brandon\_Ellis](https://forum.ansible.com/u/Brandon_Ellis)\
**Post date:** [April 18, 2021, 10:40pm UTC](https://forum.ansible.com/t/mounting-extra-k8-volumes-in-ansible-17-1/34997/2 "2021-04-18T22:40:34Z")

</div>

Never mind, figured it out. In the Ansible Installer playbook it looks like you can edit “/installer/roles/kubernetes/templates/deployment.yml.j2” and “/installer/roles/kubernetes/templates/configmap.yml.j2” with whatever config you want. Add krb5.conf, add custom logos, add loadbalancer SSL, go crazy.

---

<div class="post-metadata">

**Author:** ![Wei-Yen\_Tan](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/wei-yen_tan/32/4111_2.png) [@Wei-Yen\_Tan](https://forum.ansible.com/u/Wei-Yen_Tan)\
**Post date:** [April 18, 2021, 10:42pm UTC](https://forum.ansible.com/t/mounting-extra-k8-volumes-in-ansible-17-1/34997/3 "2021-04-18T22:42:03Z")

</div>

I thought you would add that to the crd?

---

<div class="post-metadata">

**Author:** ![Brandon\_Ellis](https://avatars.discourse-cdn.com/v4/letter/b/dec6dc/32.png) [@Brandon\_Ellis](https://forum.ansible.com/u/Brandon_Ellis)\
**Post date:** [April 20, 2021, 1:55pm UTC](https://forum.ansible.com/t/mounting-extra-k8-volumes-in-ansible-17-1/34997/4 "2021-04-20T13:55:03Z")

</div>

Not sure on that. I’d have to be editing the operator deployment in the crd (which in v 0.6 didn’t have any support for making the ingress type Loadbalancer), and I don’t think the crd allowed you to modify anything more than just the deployment volumes and mounts.
