chore: migrate Platform/BudgetPolicy CRs to *.nanohype.dev groups#1
Merged
Conversation
The eks-agent-platform operator now serves these two CRs under per-kind API groups on the nanohype.dev domain instead of a single shared agents.stxkxs.io group. Update the competitive-intelligence tenant declaration and the docs that reference it to the new groups. ─── platform.yaml ─── - BudgetPolicy apiVersion -> governance.nanohype.dev/v1alpha1 - Platform apiVersion -> platform.nanohype.dev/v1alpha1 The two CRs now sit in distinct groups: BudgetPolicy under governance, Platform under platform. Kinds, names, namespace (tenants-protohype), and every spec field are unchanged. ─── docs ─── - AGENTS.md: reword the "Two CRs under ..." prose to name both groups explicitly and fix both code-block apiVersion lines. OTel resource attributes (agents.tenant / agents.platform), chart values, and the chart itself are untouched. Verification: platform.yaml parses as multi-doc YAML; helm lint chart and helm template competitive-intelligence chart -f chart/values-staging.yaml both pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Migrate the Platform and BudgetPolicy CRs off the single shared
agents.stxkxs.io/v1alpha1group onto the per-kind groups the eks-agent-platform operator now serves.platform.yaml
BudgetPolicyapiVersion ->governance.nanohype.dev/v1alpha1PlatformapiVersion ->platform.nanohype.dev/v1alpha1The two CRs now sit in distinct groups. Kinds, names, namespace (
tenants-protohype), and every spec field are unchanged.Docs
agents.stxkxs.io/v1alpha1to name the per-kind groups.Untouched
agents.tenant/agents.platform)Verification
platform.yamlparses as multi-doc YAMLhelm lint chartpasseshelm template <name> chart -f chart/values-staging.yamlrenders cleanly