1. Proposed title of this feature request
–
Need restart policy to set pod restart count limit

2. What is the nature and description of the request?
–
Customer want to try restarting the containers for 10 times or 20 times and POD should be destroyed or should stop trying to restart further.

When set the RestartPolicy Never , it does not try to restart exited or failed Containers on the pod. Pods immediately fail and exit.
Customer do not want to set restart policy never.

3. Why does the customer need this? (List the business requirements here)
–
Customer have a Separate Secret infra, having multiple components.
All kind of secrets (ssl cert, db passwords, FID passwords, any other passwords) are stored there and a local secret agent in POD make a call to this secret Infra (outside of ECS clusters) to get those secret when needed.
There are several cases, when certain secret was not correct or was not defined properly in the POD definition or any other similar scenario, POD is not able to spin up and container inside the POD is keep on restarting every few minutes. 
Container restart policy is set to always in case failure, which is causing thousands of request every single day from each of those erroneous PODs.
Total hit to secret infra is resulting in some millions every day in general.  Above failed scenarios sometimes increase the load to double.

Customer need an option to limit the number of container restart inside a POD in such failure scenario. so POD is destroyed after certain failure threshold.

4. List any affected packages or components.
Pod