Kubernetes: Cannot edit any logos; AWX Branding Repo has no effect.

Hi, I’ve deployed AWX 17.1.0 on a Kubernetes cluster using the install playbook and I’m trying to edit the AWX branding logos to a custom one.
What I’ve tried so far:

  • Editing the logo-header.svg and logo-login.svg in \awx\ui_next\public\static\media
    • This does nothing. I realized that the svgs I was editing were of potatoes that never even displayed on the deployment, so of course my changes wouldn’t show up
  • Downloading the awx-logos repo as a sibling, editing the logos in the downloaded repo, and setting the value “awx_official=true” in the inventory.
    • This leads me to believe that the aws-logos repo never would change anything in the first place. Why is it there anyways?
  • Using the UI to manually edit the logo from within AWX.
    • Unfortunately, I get this screen, with an evil-looking smug smiley face. I thought this feature already existed long ago!

How on earth do I change the logo? At this point it seems as if it’s baked already into the Docker Image…
Given that there’s no master node in the Kubernetes deployments, and no storage volumes to access, Is there even a way to manually push the new files to the cluster???
Do I need to remake the docker image?

Have you gotten this to work? I saw you doing something with configmaps. I have tried using a DOCKERFILE to COPY images/myimages/logo-login.svg /var/lib/awx/public/static/media/logo-login.svg

I didnt get my logo to work, nor did I get the nice AWX Logo. I ended with the angry potato

Never got the angry potato.

I used k8 config maps and volume mounts to override these 4 items:
/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/ui_next/build/static/media/logo-header.svg

/var/lib/awx/venv/awx/lib/python3.6/site-packages/awx/ui_next/build/static/media/logo-login.svg

/var/lib/awx/venv/awx/lib/python3.8/site-packages/awx/ui_next/build/static/media/logo-header.svg

/var/lib/awx/venv/awx/lib/python3.8/site-packages/awx/ui_next/build/static/media/logo-login.svg

Could have also built a new image, but this method doesn’t require you to do so as long as you use a k8 cluster.

Here’s what I ended up doing for 18.0. It should probably work for 19.1 unless the paths have changed.

https://groups.google.com/g/awx-project/c/9dGPM8YUEsg/m/TtWt6QVZAgAJ

Versions 17.1 and below require you to modify the deployment.yml.j2 file instead to achieve the same effect.