Kubernetes - SecretsIf an ExternalSecret references a non-existent secret key in the external store, what is the expected behavior by default?AThe ExternalSecret controller retries until the key appearsBThe Kubernetes Secret is created with an empty value for that keyCThe ExternalSecret resource fails and no Secret is createdDThe ExternalSecret controller ignores the missing key and continuesCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand default missing key handlingBy default, if a key is missing in the external store, the controller creates the Kubernetes Secret with an empty string for that key.Step 2: Eliminate other optionsRetries or failures depend on configuration; ignoring missing keys is not default behavior.Final Answer:The Kubernetes Secret is created with an empty value for that key -> Option BQuick Check:Missing key results in empty value in Secret [OK]Quick Trick: Missing keys default to empty values in Secrets [OK]Common Mistakes:Expecting controller to fail immediatelyAssuming retries happen automaticallyThinking missing keys are ignored silently
Master "Secrets" in Kubernetes9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More Kubernetes Quizzes ConfigMaps - Creating ConfigMaps from files - Quiz 14medium ConfigMaps - Using ConfigMaps as environment variables - Quiz 12easy Health Checks and Probes - Probe timing parameters (initialDelay, period, timeout) - Quiz 1easy Health Checks and Probes - Readiness probe concept - Quiz 4medium Networking - DNS in Kubernetes (CoreDNS) - Quiz 7medium Persistent Storage - Why persistent storage matters in Kubernetes - Quiz 3easy Resource Management - Quality of Service classes (Guaranteed, Burstable, BestEffort) - Quiz 9hard Scheduling - DaemonSets for per-node workloads - Quiz 8hard Scheduling - Node selectors for simple scheduling - Quiz 10hard Secrets - Secrets are not encrypted by default - Quiz 13medium