instruction: Create a Dockerfile for Nginx with production best practices
output: ```dockerfile
  From Message
   ---- ------ ---- ---- -------
   Normal ScalingReplicaSet 12m deployment-controller Scaled up replica set nginx-deployment-75675f5897 to 3
   Normal ScalingReplicaSet 11m deployment-controller Scaled up replica set nginx-deployment-c4747d96c to 1
   Normal ScalingReplicaSet 11m deployment-controller Scaled down replica set nginx-deployment-75675f5897 to 2
   Normal ScalingReplicaSet 11m deployment-controller Scaled up replica set nginx-deployment-c4747d96c to 2
   Normal ScalingReplicaSet 11m deployment-controller Scaled down replica set nginx-deployment-75675f5897 to 1
   Normal ScalingReplicaSet 11m deployment-controller Scaled up replica set nginx-deployment-c4747d96c to 3
   Normal ScalingReplicaSet 11m deployment-controller Scaled down replica set nginx-deployment-75675f5897 to 0
   Normal ScalingReplicaSet 11m deployment-controller Scaled up replica set nginx-deployment-595696685f to 1
   Normal DeploymentRollback 15s deployment-controller Rolled back deployment "nginx-deployment" to revision 2
   Normal ScalingReplicaSet 15s deployment-controller Scaled down replica set nginx-deployment-595696685f to 0
  Scaling a DeploymentYou can scale a Deployment by using the following command:kubectl scale deployment/nginx-deployment --replicas=10
  The output is similar to this:deployment.apps/nginx-deployment scaled
  Assuming horizontal Pod autoscaling is enabled
  in your cluster, you can set up an autoscaler for your Deployment and choose the minimum and maximum number of
  Pods you want to run based on the CPU utilization of your existing Pods.kubectl autoscale deployment/nginx-deployment --min=10 --max=15 --cpu-percent=80
  The output is similar to this:deployment.apps/nginx-deployment scaled
  Proportional scalingRollingUpdate Deployments support running multiple versions of an application at the same time. When you
  or an autoscaler scales a RollingUpdate Deployment that is in the middle of a rollout (either in progress
  or paused), the Deployment controller balances the additional replicas in the existing active
  ReplicaSets (ReplicaSets with Pods) in order to mitigate risk. This is called proportional scaling.For example, you are running a Deployment with 10 replicas, maxSurge=3, and maxUnavailable=2.Ensure that the 10 replicas in your Deployment are running.kubectl get deploy
  The output is similar to this:NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
  nginx-deployment 10 10 10 10 50s
  You update to a new image which happens to be unresolvable
  ```