When writing kubernetes files is there an easy way to validate syntax or discove . . .

Stephen Nichols:
When writing kubernetes files is there an easy way to validate syntax or discover possible values while editing it? The format seems so arcane and prone to errors of capitalization, pluralization of words, or not knowing required field values. Looking it up one element at a time in kubernetes docs is very slow and tedious.

Randy McCright:
Outside of the exam, there are a variety of tools to do this easily. For the exam your just using VI which is a basic text editor and has no context.

Randy McCright:
You can do things such as

kubectl explain deployment.spec.template.spec

Randy McCright:
But to me that’s even more tedious than copy-paste from examples and do a small amount of tweaking.

Stephen Nichols:
Without a better way it looks like I have no choice but to memorize all possible configurations. That is going to be painful.

Daz Mac:
Use imperative commands to generate the yaml and then edit it during the exam. For real world vscode has kubernetes plugin.

R Banerjee:
Or make a bookmark folder for all examples ( too tedious, but quickest to resolve in the exam )