Sudi Krishnakumar:
Hello!
Whilst looking at the solution videos from Mumshad, majority of the yaml that we need to create manually (for PV and PVC for instance) are copied from the Kubernetes documentation pages. In exam though, would we have the time and privilege to do this? I know it is an open book exam, but do we actually lose time if we were to look for yaml on the Kubernetes documentation page? Thanks!
Marko Eremija:
well, there is no other way unless you memorize all the fields 
Bhaskar Bantupalli:
copy pv, pvc, pod all three file separated by - - - (3 hyphens)
Marko Eremija:
and yes, if you manage your time accordingly, copy+paste from the kubernetes docs is more than enough
Sudi Krishnakumar:
Thanks guys, I was under the impression that it is actually required to memorise the field names (which obviously is a nightmare)
Marko Eremija:
haha, no way especially if you don’t have an IDE like VScode handy
unnivkn:
Hi @Sudi Krishnakumar practice imperative commands as much as you can, to avoid declarative statements/k8s doc. However few resource like pv, pvc, sa, netpol etc you have to depend on k8s doc/kubectl explain.
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#create
Al West:
I heavily used imperative commands with the -o yaml --dry-run=client option piped to a file > - then you can edit the yaml and use kubectl to apply.