Skip to content

Unpack Job doesn't use the nodeSelector property #2977

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

Open
Mezzenine opened this issue Jun 13, 2023 · 0 comments
Open

Unpack Job doesn't use the nodeSelector property #2977

Mezzenine opened this issue Jun 13, 2023 · 0 comments

Comments

@Mezzenine
Copy link

Type of question

Help or a workaround.

Question

The current release 0.24.0 doesn't contain this fix #2685.
My question: Is there a workaround or any other possibility to temporarily fix this, until the next release is dropped

What did you do?
I'd like to deploy the keycloak-operator via OLM in a mixed (Linux/Windows) AKS Cluster.

What did you expect to see?
The unpack job should be assigned to a Linux node.

What did you see instead? Under which circumstances?
The unpack job is infinite pending because it is assigned to a Windows node.

Environment

  • operator-lifecycle-manager version: 0.24.0
  • Kubernetes version information: 1.25.6
  • Kubernetes cluster kind: AKS

Additional context
Add any other context about the question here.

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

1 participant