 this video we're going to talk about setting environment variables and one very common use case is to use environment variables to override log levels. So let me toggle over to IntelliJ real quick. So you can see here for this application, the application properties that's getting deployed. So I have everything in a package called Guru Spring Framework SFG Rust Brewery and that is at a debug level right now. So let me come back over to the command line and we can do cube CTL get all and let's do cube CTL logs and we'll pass it in the ID of this container and here we can see in my beer loader we are getting loading initial initial data so count is zero. Let's see that we have the started started that but the primary one is here we have count is zero and this is from Guru Spring Framework Rust Brewery Bootstrap and we can see this is log output and we are at a debug level so we can see that right in the log data and for deployment a lot of times development wise we loved getting log data at a debug level but when we have stuff running in production obviously that's not something that we want so what we can do is clear this in here let's come in and edit the deployment like so and come down here and in the containers there's actually we can actually set a another property and that is going to be here. I'm going to come in actually I want to use spaces here for YAML. I'm going to say ENV and this is going to take a name value pair as a list of different environment properties that we are going to be setting and here what I want to do is say name and what we want to do is for the properties that we set in our property file it's going to be all uppercase with an underscore so we'll do logging so that is going to be the environment property name and then we give it another property for the value creatively name value and in this case we're going to switch it to the info log level so this sets up the environment property and again just remember in our property files we're going to have name dot dot name here we're going to go name underscore name so logging underscore level underscore guru package name and then the value of info so let's go ahead and write that and here another thing we can do what we can do here is we do have that up and running we can see that's going for six minutes we can do apply minus F and this is going to tell Kubernetes to go ahead and reapply that it's changes and it will cause that container to restart with a new environment variable and we see they get all and here you can see one pod is terminating and another one is starting so let's grab this one and it actually started up before I could get that command in but you can see now the debug log information is no longer there so that environment property has been applied to the container and we've changed the log level of our spring boot application so now we are not dumping that debug information into our container log so again this is very common use case so when we have stuff that we're debugging locally as a developer obviously we like that when we are running in a deployment environment typically we don't want to have all that debug log data going through our system so I clear this and just take a quick look at that you can see down here on the bottom for our spec on the containers we edited this file and we put in the property ENV which is going to take a list of environment variables and that is going to be setting up the log level for my package to info overriding what is in our spring boot deployment artifact