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

operator-controller settings not working #36

Open
psolomon-services opened this issue Jan 21, 2025 · 3 comments
Open

operator-controller settings not working #36

psolomon-services opened this issue Jan 21, 2025 · 3 comments

Comments

@psolomon-services
Copy link

psolomon-services commented Jan 21, 2025

I'm trying to scale the AWX controller manager, not the web or task pods. According to the docs,
I can set this in the operator-controller section, as follows (in column 1):

From my values.txt file:

operator-controller:
  spec:
    replicas: 2

This does not work (the controller manager count remains at one instance). Is this a bug, or just not documented properly (meaning I have it improperly formatted in my values.txt file)? I've looked at the helm code and seems like it should work. I would prefer not to patch or scale after the initial creation.

I'm currently running Version 2.19.0 of the awx-operator. I'm using an external Postgres instance (a pod in this POC).

$ kubectl get all,ing -n awx
NAME                                              READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/awx-operator-controller-manager   1/1     1            1           114s
deployment.apps/awx-poc-task                      1/1     1            1           100s
deployment.apps/awx-poc-web                       2/2     2            2           100s

NAME                                                      TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)    AGE
service/awx-operator-controller-manager-metrics-service   ClusterIP   10.96.52.209   <none>        8443/TCP   114s
service/awx-poc-service                                   ClusterIP   10.96.41.62    <none>        80/TCP     101s
service/postgres-service                                  ClusterIP   10.96.180.50   <none>        5432/TCP   2m19s

NAME                                                   READY   STATUS      RESTARTS   AGE
pod/awx-operator-controller-manager-76685d6ff4-65lj9   2/2     Running     0          114s
pod/awx-poc-migration-24.6.0-6pht8                     0/1     Completed   0          91s
pod/awx-poc-task-78658dd859-7522x                      4/4     Running     0          100s
pod/awx-poc-web-765598d874-q5kht                       3/3     Running     0          100s
pod/awx-poc-web-765598d874-rzddg                       3/3     Running     0          100s
pod/postgres-awx-0                                     1/1     Running     0          2m19s

NAME                                 STATUS     COMPLETIONS   DURATION   AGE
job.batch/awx-poc-migration-24.6.0   Complete   1/1           58s        91s

NAME                            READY   AGE
statefulset.apps/postgres-awx   1/1     2m19s

NAME                                               CLASS   HOSTS                      ADDRESS     PORTS     AGE
ingress.networking.k8s.io/awx-poc-awxapi-ingress   nginx   awx.myhost.com      localhost   80, 443   101s

=================================
$ helm version
version.BuildInfo{Version:"v3.16.2", GitCommit:"13654a52f7c70a143b1dd51416d633e1071faffb", GitTreeState:"dirty", GoVersion:"go1.23.2"}
                                                                                                                               
$ kubectl version                                                                                                                                                                                                                                                    Client Version: v1.30.5
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3                                                                                                                                                                                                              Server Version: v1.31.0                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

$ uname -a
Darwin mypc 24.2.0 Darwin Kernel Version 24.2.0: Fri Dec  6 19:00:33 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T8122 arm64 
@schen1
Copy link
Collaborator

schen1 commented Jan 22, 2025

Hi @psolomon-services

Thanks for opening this issue. We are still not yet done with the new release process, that's probably why this is not yet available, especially in 2.19.0.

Do you have a specific need to use 2 replicas for the operator controller? Usually 1 replica is enough.

Cheers

@psolomon-services
Copy link
Author

We have a requirement from our Architecture team for this. We would also like to use this feature to override other things, like the controller name (which doesn't match our prefixes set by the helm chart).

Something like this (if that will support this feature):

operator-controller:
  metadata:
    name:  my-new-awx-controller-manager

Do you know when this feature will be available?

@miles-w-3
Copy link
Collaborator

Releases will be possible as soon as #35 is merged

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

No branches or pull requests

3 participants