feat: add package configuration to node config map #97
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.
Agents/steps need runtime context (agent version, package info). Previously node metadata CMs had only labels/annotations.
- Implementation:
packages.jsonto each node’s “metadata” ConfigMap:agentVersion(parsed from operatorAgentImage)packages: name, version, image, optionalagentImageOverride/interrupt/configInterruptsValidateNodeConfigmapsAgentVersion()helper onSkyhookOperatorOptions.SkyhookMetadataintermediary (decoupled from CRD shape).- Tests:
skyhooknamespace exists.packages.jsonexists withagentVersion, package names/versions.