LogoLogo
Self-Managed Articles
Self-Managed Articles
  • IHC Related
    • Special characters in passwords breaks Prisma migrations
    • IMDSv2 Suport on AWS and Immuta
    • Restore & DR for external database’s in Azure & AWS (IHC)
    • Migration/ Install to External Database fails with: "migrations found.."
    • Installing Kubernetes via `helm install` using a SHA instead of image tag
    • Relation "Token" does not exist
    • Replacing the Packaged Ingress Controller from the IHC
  • IEHC Related
    • Audit pod is restarting with "prisma migrations..." related errors on fresh installation
    • Disaster Recover Considerations for Self-Managed Immuta Deployments
  • FAQ
    • How to schedule pods on specific nodes?
    • What to do if the pg_wal directory is full? (IHC)
    • How do I gather Bometadata/Immuta query output as a file?
    • Where does Immuta put its logs and other logging related files?
    • Large disk space usage due to pgsql_tmp files
    • Disaster Recovery scenarios with self-managed Deployments (IHC)
Powered by GitBook
On this page
  1. FAQ

How to schedule pods on specific nodes?

When installing Immuta you can place the pods on whichever nodes are readily available, sometimes if you wish to specify the correct nodes to install pods on you can use nodeSelector to specify that.

Use the following under the desired section of your immuta-values.yaml file:

nodeSelector:
  agentpool: apppool0
PreviousDisaster Recover Considerations for Self-Managed Immuta DeploymentsNextWhat to do if the pg_wal directory is full? (IHC)

Last updated 5 months ago