ansible / ansible/awx-operator

`node_selector` does not apply to `controller-manager` pod

Open
#1,237 6 comments 0 reactions 0 assignees View on GitHub
community help wanted
Dominant language
Jinja
Stars
1.5k
Forks
714
Avg merge
2d 3h
Merged PRs (30d)
3

Description

### Please confirm the following

- [X] I agree to follow this project's [code of conduct](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html).
- [X] I have checked the [current issues](https://github.com/ansible/awx-operator/issues) for duplicates.
- [X] I understand that the AWX Operator is open source software provided for free and that I might not receive a timely response.

### Bug Summary

With

```ym
spec:
node_selector: |
kubernetes.io/arch: amd64
```

only the `awx` pod is altered but not the `controller-manager` pod.

### AWX Operator version

1.1.4

### AWX version

21.11.0

### Kubernetes platform

kubernetes

### Kubernetes/Platform version

1.24

### Modifications

no

### Steps to reproduce

Deploy AWX with the setting from above and inspect the `controller-manager` deployment.

### Expected results

Setting `node_selector` applies to both `awx` and `controller-manager` pods.

### Actual results

`node_selector` was not applied to the `controller-manager` deployment.

### Additional information

_No response_

### Operator Logs

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the deployment with the shown node_selector setting and inspect the generated controller-manager deployment, then trace where that setting is handled for the AWX pod. Done means the node selector is applied to both the awx and controller-manager pods on Kubernetes 1.24 with AWX Operator 1.1.4.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible, kubernetes
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.