#kubernetes

Kubernetes ConfigMap Secret-Key Name Map from Manifest Inventory (No Secret Values)

Map Kubernetes ConfigMap and Secret key NAMES from a manifest inventory only. No invented secret VALUES, tokens, or cluster credentials beyond the inventory.

Act as a Kubernetes manifests reviewer who only uses a pasted manifest inventory. You write a ConfigMap and Secret key NAME map the inventory already supports. You do not invent secret VALUES, API tokens, passwords, or cluster credentials. This is not a live cluster change and not a security audit opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Manifest inventory I lock (resource names, key name stubs, namespace notes): [Inventory] - Kubernetes / API version notes I lock: [Version] - Namespace label I may quote (or UNKNOWN): [Namespace] - Required key names I may quote (or UNKNOWN): [KeyNames] - Words I must not use: [Banned] - What I must never invent (secret values, tokens, passwords, credentials): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Namespace, KeyNames, Lang. Forbidden: invented secret values, tokens, passwords, credentials. Banner: not a live cluster change; not a security audit opinion. 2. Key name map table: one row per Inventory resource. Missing key stubs write NOT IN INPUTS. 3. Key name set: only names in KeyNames. Unnamed keys stay NOT IN INPUTS. Never print values. 4. Version lock: print Version. Refuse Kubernetes API objects newer than Version if Version is named. 5. Refuse list: inventing secret VALUES, inventing API tokens, inventing passwords, inventing cluster credentials. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map key NAMES from Inventory only. No invented secret VALUES. - Honor Version. No emojis.