search

ansible / awx-operator

An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
https://www.github.com/ansible/awx
Apache License 2.0
1.24k stars 628 forks source link

Closed Environments override images other than ee_images #1156

Open trippinnik opened 1 year ago

trippinnik commented 1 year ago

Please confirm the following

Feature type

New Feature

Feature Summary

In closed environments there is no direct access to internet and images need to be pulled from local repos like artifactory or pulp.

Now helm chart awx operator deployment file deployment-awx-operator-controller-manager.yaml has hard-coded values for images:

image: gcr.io/kubebuilder/kube-rbac-proxy:v0.13.0 name: kube-rbac-proxy

name: awx-manager image: quay.io/ansible/awx-operator:1.11

Select the relevant components

Steps to reproduce

deploy in closed environment and fails

Current results

failure to delploy

Sugested feature result

ability to deploy using local repositories as defined in values or chart

Additional information

No response

akus062381 commented 1 year ago

@miles-w-3 is this something you might be willing to help out with? :-)

rooftopcellist commented 1 year ago

From our conversation in Matrix, you can modify the registry for the kube-rbac-proxy image via the kustomization.yaml file that deploys the awx-operator. For example:

However, I am not entirely sure how this would work with helm. Helm uses the kustomization.yaml file as well under the hood, but I think you would have to create your own custom helm chart with those changes.

miles-w-3 commented 1 year ago

You should just be able to make the changes @rooftopcellist mentioned above to the kustomization.yaml, commit them on your fork, and then just runmake helm-chart

trippinnik commented 1 year ago

Yes, I did the fork, make method as miles suggested.

I guess good to know that more is available through kustomization than helm directly, but was a little less clear in the docs

On Wed, Dec 14, 2022, 6:14 PM Miles @.***> wrote:

You should just be able to make the changes @rooftopcellist https://github.com/rooftopcellist mentioned above to the kustomization.yaml, commit them on your fork, and then just runmake helm-chart

— Reply to this email directly, view it on GitHub https://github.com/ansible/awx-operator/issues/1156#issuecomment-1352346238, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2HEVWR24XVN7JBURIZ53WNJIEJANCNFSM6AAAAAAS6ZNWT4 . You are receiving this because you authored the thread.Message ID: @.***>

codepoke-kk commented 1 year ago

I am in the same boat as trippinnik. My company has closed the Internet and I'm pulling everything from Artifactory internally. I have a lot of it working after 3 weeks of misery, but I have a ton left to go.

The way I got the good stuff to happen is I piped Kustomize to a text file and commenced to tweaking. I now have 1300 lines that kind of work, but I need to understand what I can modify and where. I'm trying to replicate work done by the previous admin who left us with no documents, so I'm coming in very cold. We have 7 AWX namespaces installed, all using LDAP authentication, our own certificate CA signer, a custom EE, and dozens of other goodies, but back on 20.0.1 which had bugs we cannot tolerate. So, I've got a lot of work ahead of me. I can post the EE error I'm seeing now, but I really need a core understanding of what can and cannot be done in this configuration file. Where can I find that?

Thank you.

Kevin

codepoke-kk commented 1 year ago

FWIW, the EE error (it always takes me a little while to find errors in OpenShift, because I'm so new to containers) is:

1 line
Error: error loading config file: field firewallrules not defined for command node: unknown field name firewallrules

I have zero clue where to define a firewall rules field, nor how to define there.