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

Add nodeSelector linux to Deployment and StatefulSet #8141

Open
MariusGrandeAndersen opened this issue Jan 11, 2022 · 3 comments
Open

Add nodeSelector linux to Deployment and StatefulSet #8141

MariusGrandeAndersen opened this issue Jan 11, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@MariusGrandeAndersen
Copy link

MariusGrandeAndersen commented Jan 11, 2022

Summary

Change installation so all pods are created on linux nodes.

Motivation

We have a Kubernetes cluster with both windows and linux nodes. Without nodeSelector the pods will randomly be created on the windows node, and will fail pulling down the container image.

Currently I have to download the manifest, edit the deployments and statefulsets, then run "kubectl apply" on my local file, and add it manually. However when I will upgrade to a new version of argocd I will have to do this process again.

(The same goes for the applicationset).

Proposal

As argocd only works on Linux,
add

      nodeSelector:
        "kubernetes.io/os": linux

to all Deployments and StatefulSets.

@MariusGrandeAndersen MariusGrandeAndersen added the enhancement New feature or request label Jan 11, 2022
@saumeya
Copy link
Contributor

saumeya commented Mar 1, 2022

Hi @mariusandersen, can you try using nodePlacement property in ArgoCD - https://argocd-operator.readthedocs.io/en/latest/reference/argocd/#nodeplacement-option . This can help you specify the nodeSelector which will get applied to all deployments and statefulSets.

@BrunoJuchli
Copy link

BrunoJuchli commented Jun 9, 2022

@saumeya
Thank you for the hint.
Do I understand correctly that the nodeplacement option is only available when Argo CD operator is installed?

(Argo CD operator in turn should be installed on OpenShift 4 which then again requires at least 40 cores.)

@rishabh625
Copy link
Contributor

@BrunoJuchli this nodeselector is specific to your environment , I may have a Linux machine but I may label that node differently it doesn't makes sense to me to add this specific selector in manifests and yeah operator helps u automate that ,also is operator taking 40 cores of cpu?

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

No branches or pull requests

4 participants