Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWX Operator doesn't respect when a image_pull_secrets is specified, creates redhat-operator-pull-secret regardless. #1848

Open
3 tasks done
dticknor1 opened this issue May 1, 2024 · 2 comments

Comments

@dticknor1
Copy link

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that the AWX Operator is open source software provided for free and that I might not receive a timely response.

Bug Summary

The Deploying a specific version AWX documentation lists that an "image_pull_secrets" value can be specified to use a custom container image pull secret.

However, the operator does not respect this, and creates the redhat-operators-pull-secret regardless of if the above spec is specified.

This causes duplication of pull secrets, with the custom and the default image pull secret being created.

Proposing that we add a when condition to https://github.com/ansible/awx-operator/blob/devel/playbooks/awx.yml#L29 to only create the redhat-operator-pull-secret when image_pull_secrets is null.

AWX Operator version

2.12.2

AWX version

23.6.0

Kubernetes platform

kubernetes

Kubernetes/Platform version

1.28

Modifications

yes

Steps to reproduce

specify a custom image location and a image_pull_secrets

Expected results

When a custom image_pull_secrets is specified, the operator should utilize this pull secret, and not create the default redhat-operators-pull-secret

Actual results

The redhat-operators-pull-secret is created regardless of whether a custom image_pulls_secret is specfied.

Additional information

No response

Operator Logs

No response

@kurokobo
Copy link
Contributor

kurokobo commented May 1, 2024

@dticknor1
F.Y.I., redhat-operators-pull-secret is for the Operator itself and not for any AWX related pods:

imagePullSecrets:
- name: redhat-operators-pull-secret

The secret is completely independent of image_pull_secrets and is completely dummy as a workaround to avoid kubelet to report errors.

Contexts:

This is valid RFE and it is preferable to have no dummy secrets, but there is no real harm if there is.

@Keith-Nowosielski-SJSU
Copy link

@dticknor1 F.Y.I., redhat-operators-pull-secret is for the Operator itself and not for any AWX related pods:

imagePullSecrets:
- name: redhat-operators-pull-secret

The secret is completely independent of image_pull_secrets and is completely dummy as a workaround to avoid kubelet to report errors.
Contexts:

This is valid RFE and it is preferable to have no dummy secrets, but there is no real harm if there is.

Are you sure? I'm currently trying to stand up new deployment (really migrate but I can't even get a new deployment up).
I'm getting this issue.

Warning FailedToRetrieveImagePullSecret Pod/awx-operator-controller-manager- Unable to retrieve some image pull secrets (redhat-operators-pull-secret); attempting to pull the image may not succeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants