Flux CD
Hard
Security
You replaced the age public key in .sops.yaml during a key rotation. Which command makes existing encrypted files readable with the new key without changing their values?
Select your answer:
Show answer and explanation
Answer: sops updatekeys on each file
Explanation
sops updatekeys re-encrypts each file's data key for the recipients now listed in .sops.yaml and leaves the encrypted values as they are. sops rotate does something else: it generates a new data key and re-encrypts every value, which you add when a key may have leaked. Both need a private key that can decrypt the file today.
More hard Flux CD questions
- A .sops.yaml has a rule with path_regex: .*\.yaml$ followed by a rule with path_regex: ^prod/.*\.yaml$. Which rule applies when you encrypt prod/db.yaml?
- What does the annotation kustomize.toolkit.fluxcd.io/ssa: IfNotPresent do on an object in a Flux source?
- A change to an immutable field makes Flux's apply of a Job fail. Which annotation on the Job tells Flux to delete and recreate it?
- A GitRepository has no ref field, and the repository's default branch is main. What does Flux check out?
- kustomize-controller can't tell when a custom resource from a third-party operator is healthy. How do you teach it?
- You want to delete a Flux Kustomization but keep the workloads it created running. Which field do you set first?