feat: inject job info as envvars in scheduled pods #4473
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
What type of PR is this?
Feature PR which injects two environment variables into all containers of gang-scheduled jobs when they have node uniformity requirements:
If any envvar was already defined, Armada will not override it.
What this PR does / why we need it:
By injecting job info, Armada integrations like armada-spark could implement dynamic allocation where the initial set of driver + executors gets submitted as a non-preemptible gang, and the dynamic executors then use the gang info to leverage
nodeSelectorsto submit dynamic preemptible executors on the same set of nodes on which the initial gang is executing.Which issue(s) this PR fixes:
Fixes #4455
Testing
armadactl create queue queue-aarmadactl submit example/example-job.yamlkubectl describe <pod>