Inorder to schedule nodes, we use nodeselector type in the deployment.yaml file Ex:- nodeselector: type: ssd This will pick the node which has ssd type from the available replicas or nodepools
@deepakpatil505910 күн бұрын
Stateful and Stateless : I prepared my notes in this way. Stateful - The applications which need the last execution transactions or feeds even after restart or refresh are called stateful application Ex:- Database that's the reason we mount volumes in the deployment.yaml Stateless: The applications which don't require any last execution transactions after restart are called Stateless applications. Ex: Front end applications. we do not mount volumes unless it is necessary for application deployment.yaml file
@vishnusai465810 күн бұрын
Nice content @TQ
@salmaanshaik849210 күн бұрын
hii sir great video..... pls bring more videos like this it is very useful to overcome interview fear
Thanks Ashok , it was a quick knowledge refresher .
@Ajaybolakonda13 күн бұрын
Great video, very easy to understand.
@jovanhimal66916 күн бұрын
I thought, you would focus more in depth to security stuffs DevSecOps, vs regular DevOps, as we move to more higher tier DataCenters, the sec portion of DevOps comes very very vital
@AshokKumar-DevOps16 күн бұрын
Will start the devsecops series, soon
@Riteshdhapatepatil96617 күн бұрын
Most valuable video bro❤
@durairajgopal327718 күн бұрын
It was explained about aws resources like vpc concept as well thanks guru ji❤🎉
@trinadhmarni830019 күн бұрын
The interview is very easy, but kubernetes questions are really good
@logeshvaran2219 күн бұрын
mail id tell me
@logeshvaran2219 күн бұрын
03:11:07.293 INFO Total time: 11.536s [Pipeline] } [Pipeline] // withSonarQubeEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (OWASP Dependency) [Pipeline] tool [Pipeline] envVarsForTool [Pipeline] tool [Pipeline] envVarsForTool [Pipeline] withEnv [Pipeline] { [Pipeline] dependencyCheck [ERROR] One or more fatal errors occurred [ERROR] Unable to connect to the database - if this error persists it may be due to a corrupt database. Consider running `purge` to delete the existing database ERROR: Mark build as failed because of exit code 13 [Pipeline] dependencyCheckPublisher Collecting Dependency-Check artifact Unable to find Dependency-Check reports to parse [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Verify Dependency Report) [Pipeline] tool [Pipeline] envVarsForTool [Pipeline] tool [Pipeline] envVarsForTool [Pipeline] withEnv [Pipeline] { [Pipeline] sh + ls -l target/ total 12 drwxr-xr-x 6 jenkins jenkins 4096 Jan 9 03:10 classes drwxr-xr-x 3 jenkins jenkins 4096 Jan 9 03:10 generated-sources drwxr-xr-x 3 jenkins jenkins 4096 Jan 9 03:10 maven-status [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: FAILURE