# Correct way to "reconfigure" AWX using awx-operator on k3s **URL:** \ **Category:** AWX Project\ **Tags:** awx\ **Created:** [July 14, 2022, 8:33am UTC](https://forum.ansible.com/t/correct-way-to-reconfigure-awx-using-awx-operator-on-k3s/36848 "2022-07-14T08:33:27Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![andybourges](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@andybourges](https://forum.ansible.com/u/andybourges)\ **Post date:** [July 14, 2022, 8:33am UTC](https://forum.ansible.com/t/correct-way-to-reconfigure-awx-using-awx-operator-on-k3s/36848/1 "2022-07-14T08:33:27Z")
Hi everybody, …looking at the operator docs, I cannot find a way to reconfigure the running awx instance. I want to change the default control\_plane\_ee\_image, but keep projects/templates I have created in awx so far. What would be the recommended way to do that? Thanks in advance, Andreas ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [July 20, 2022, 8:12pm UTC](https://forum.ansible.com/t/correct-way-to-reconfigure-awx-using-awx-operator-on-k3s/36848/2 "2022-07-20T20:12:32Z")
You can add custom ee-images to the awx-demo.yml spec (or equivalent), check out “ee\_images” here [https://github.com/ansible/awx-operator#deploying-a-specific-version-of-awx](https://github.com/ansible/awx-operator#deploying-a-specific-version-of-awx) This change would not affect any resources you have in your database (projects/templates/orgs/users etc) Let us know if that helps! AWX Team ---
**Author:** ![andybourges](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@andybourges](https://forum.ansible.com/u/andybourges)\ **Post date:** [July 21, 2022, 12:14pm UTC](https://forum.ansible.com/t/correct-way-to-reconfigure-awx-using-awx-operator-on-k3s/36848/3 "2022-07-21T12:14:33Z")
Hi, …thanks for your response – highly appreciated! You can add custom ee-images to the awx-demo.yml spec (or equivalent), check out “ee\_images” here [https://github.com/ansible/awx-operator#deploying-a-specific-version-of-awx](https://github.com/ansible/awx-operator#deploying-a-specific-version-of-awx) This change would not affect any resources you have in your database (projects/templates/orgs/users etc Let us know if that helps! AWX Team OK, I already _ **have** _ the custom-ee defined in the UI for the jobs. This works. What I need is to change the control-plane image, that is used to update the code repositories. This cannot be done via UI, it seems it has to be defined somewhere else. Regarding you suggestion – I added the custom\_ee to my awx-deploy.aml: ee\_images: - name: nautobot-custom-awx-ee image: [registry.gitlab.com/nautobot1/awx-ee:3.0](http://registry.gitlab.com/nautobot1/awx-ee:3.0) First question – how can I add credentials for that registry? Nothing mentioned for EE in the docs? Anyway – once this has been done – what exactly is the process of applying this to my already running awx instance? I did: kubectl config set-context --current --namespace=awx kubectl apply -f awx-deploy.yml [awx.awx.ansible.com/awx](http://awx.awx.ansible.com/awx) configured Should I notice any change in AWX? Still looks all the same: ![](https://us1.discourse-cdn.com/ansible/original/2X/0/0865b8dc819837d4ba5e2d49674c618f082011ec.png) Thanks, Andreas ---
**Author:** ![kurokobo1](https://avatars.discourse-cdn.com/v4/letter/k/f0a364/32.png) [@kurokobo1](https://forum.ansible.com/u/kurokobo1)\ **Post date:** [July 21, 2022, 1:04pm UTC](https://forum.ansible.com/t/correct-way-to-reconfigure-awx-using-awx-operator-on-k3s/36848/4 "2022-07-21T13:04:00Z")
Hi, > What I need is to change the control-plane image, You can use control\_plane\_ee\_image instead of ee\_images. Refer “Control plane ee from private registry” section in the docs: [https://github.com/ansible/awx-operator/blob/0.25.0/README.md#control-plane-ee-from-private-registry](https://github.com/ansible/awx-operator/blob/0.25.0/README.md#control-plane-ee-from-private-registry) > First question – how can I add credentials for that registry? Nothing mentioned for EE in the docs? You can specify imagePullSecret for deployment via image\_pull\_secrets parameter, as explained in the same section as above. > I did: > kubectl config set-context --current --namespace=awx > kubectl apply -f awx-deploy.yml > [awx.awx.ansible.com/awx](http://awx.awx.ansible.com/awx) configured Correct, apply your new awx-deploy,yml and just wait 🙂 While waiting, it is recommended to watch the Operator’s logs so that you are able to recognize failure. Regards, @kurokobo > **(attachments)** > > ![image001.png](https://us1.discourse-cdn.com/ansible/original/2X/0/0865b8dc819837d4ba5e2d49674c618f082011ec.png) ---
**Author:** ![andybourges](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@andybourges](https://forum.ansible.com/u/andybourges)\ **Post date:** [July 21, 2022, 3:11pm UTC](https://forum.ansible.com/t/correct-way-to-reconfigure-awx-using-awx-operator-on-k3s/36848/5 "2022-07-21T15:11:32Z")
Hi, …thanks for assisting me here. Still no luck ☹ My awx-deploy.yaml looks like this: apiVersion: [awx.ansible.com/v1beta1](http://awx.ansible.com/v1beta1) kind: AWX metadata: name: awx spec: service\_type: nodeport projects\_persistence: true projects\_storage\_access\_mode: ReadWriteOnce **control\_plane\_ee\_image:** **- name: nautobot-custom-awx-ee** **image: [registry.gitlab.com/nautobot1/awx-ee:3.0](http://registry.gitlab.com/nautobot1/awx-ee:3.0)** web\_extra\_volume\_mounts: | - name: static-data mountPath: /var/lib/projects extra\_volumes: | - name: static-data persistentVolumeClaim: claimName: static-data-pvc …and I created an according secret (at least I hope that’s correct): kubectl create secret docker-registry nautobot-custom-awx-ee-cp-pull-credentials \ –docker-server=[registry.gitlab.com](http://registry.gitlab.com) \ –docker-username=xxxxxxx \ –docker-password=‘xxxxxx’ \ [–docker-email=andy@xxx.xx](mailto:--docker-email=andy@xxx.xx) …which gave me: „secret/nautobot-custom-awx-ee-cp-pull-credentials created” But when I try to apply the awx-deploy.yaml: # kubectl apply -f awx-deploy.yml error: error validating “awx-deploy.yml”: error validating data: ValidationError(AWX.spec.control\_plane\_ee\_image): invalid type for com.ansible.awx.v1beta1.AWX.spec.control\_plane\_ee\_image: got “array”, expected “string”; if you choose to ignore these errors, turn validation off with --validate=false Looks like I need to provide a string instead if a list of dicts here? Only the name and define the desired image above es custom EE image? Sorry for my struggling, but it seems that I’m still scratching the surface only ☹ Thanks, Andreas > **(attachments)** > > ![image001.png](https://us1.discourse-cdn.com/ansible/original/2X/0/0865b8dc819837d4ba5e2d49674c618f082011ec.png) ---
**Author:** ![andybourges](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@andybourges](https://forum.ansible.com/u/andybourges)\ **Post date:** [July 21, 2022, 3:34pm UTC](https://forum.ansible.com/t/correct-way-to-reconfigure-awx-using-awx-operator-on-k3s/36848/6 "2022-07-21T15:34:04Z")
HA – now it works! Changed the awx-deploy a bit and… ![](https://us1.discourse-cdn.com/ansible/original/2X/5/5bb12bdae12094b76fa3df7d578ea2d77597906b.png) ee\_images: - name: nautobot-custom-awx-ee image: [registry.gitlab.com/nautobot1/awx-ee:3.0](http://registry.gitlab.com/nautobot1/awx-ee:3.0) control\_plane\_ee\_image: [registry.gitlab.com/nautobot1/awx-ee:3.0](http://registry.gitlab.com/nautobot1/awx-ee:3.0) Thanks so much for your patience and assistance! Andreas > **(attachments)** > > ![image001.png](https://us1.discourse-cdn.com/ansible/original/2X/0/0865b8dc819837d4ba5e2d49674c618f082011ec.png) ---
**Author:** ![andybourges](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@andybourges](https://forum.ansible.com/u/andybourges)\ **Post date:** [July 22, 2022, 4:29am UTC](https://forum.ansible.com/t/correct-way-to-reconfigure-awx-using-awx-operator-on-k3s/36848/7 "2022-07-22T04:29:15Z")
Moving forward here – I changed the registry from the official [gitlab.com](http://gitlab.com) to a docker-based registry server at the customer network. For the “normal” EE entry, that worked out of the box, since we can disable ssl\_verification when configuring the EE. But for the control-plane image, I’m unable to figure out, how to disable ssl-verify? Do I have to specify this flag, when creating the secret? kubectl create secret docker-registry xxxxxx-awx-ee-cp-pull-credentials --docker-server=10.40.xx.xxx:4443 --docker-username=awx --docker-password=‘xxxxxx’ in the container logs I see: x509: cannot validate certificate for 10.40.xx.xxx because it doesn’t contain any IP SANs The certificate is self-signed and has no SANs. I faced the same message when interacting with the registry on cli, but fixed it by adding the following to the docker-config: { “insecure-registries” : [“10.40.xx.xxx:4443”] } Is there a similar knob in awx to turn off ssl verification for the control-plane image? Thanks, Andreas > **(attachments)** > > ![image002.png](https://us1.discourse-cdn.com/ansible/original/2X/5/5bb12bdae12094b76fa3df7d578ea2d77597906b.png) > ![image001.png](https://us1.discourse-cdn.com/ansible/original/2X/0/0865b8dc819837d4ba5e2d49674c618f082011ec.png)