💻 Coding
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.
0Reviews
Prompt
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.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
Inventory: ConfigMap quay-app-config as pasted key stub LOG_LEVEL as pasted namespace note harbor-ops as pasted; Secret river-db-creds as pasted key stub DB_USER as pasted. Secret VALUE NONE. Token NOT IN INPUTS. Version: Kubernetes 1.29 core/v1 as pasted (do not invent 1.32 ValidatingAdmissionPolicy merge) Namespace: harbor-ops as pasted KeyNames: LOG_LEVEL as pasted; DB_USER as pasted. DB_PASSWORD key name UNKNOWN. Banned: guaranteed secure, value invent, token invent, password invent Never: invent secret values, invent tokens, invent passwords, invent credentials Format: ledger + table + keynames + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: ConfigMap quay-app-config key stub LOG_LEVEL namespace harbor-ops; Secret river-db-creds key stub DB_USER. Secret VALUE NONE. Token NOT IN INPUTS. Version Kubernetes 1.29 core/v1. Namespace harbor-ops. KeyNames LOG_LEVEL; DB_USER; DB_PASSWORD key name UNKNOWN. Lang English. Banner: not a live cluster change; not a security audit opinion. Forbidden: invented secret values, tokens, passwords, credentials, guaranteed secure, value invent, token invent, password invent. 2. Key name map. 1. quay-app-config | kind ConfigMap as pasted | key LOG_LEVEL as pasted | namespace harbor-ops as pasted | value NOT PRINTED / NONE. 2. river-db-creds | kind Secret as pasted | key DB_USER as pasted | namespace harbor-ops as pasted | value NOT PRINTED / NONE. Token NOT IN INPUTS so no token row. Passwords not invented. 3. Key name set. LOG_LEVEL; DB_USER as KeyNames. DB_PASSWORD key name UNKNOWN so write DB_PASSWORD name NOT IN INPUTS. No secret VALUES printed. No third key invented. 4. Version lock. Kubernetes 1.29 core/v1 as pasted. 1.32 ValidatingAdmissionPolicy merge objects not used. Cluster UUID NOT IN INPUTS. 5. Refuse. Secret value invent: refused. Token invent: refused. Password invent: refused. Credential invent: refused. Guaranteed secure: refused. 6. Compliance. Banned hits none. Format ledger+table+keynames+version+refuse+compliance. Gaps: DB_PASSWORD key name decision, mount paths, immutable flag, sealed-secret path, owner labels. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.