anchor.diff:  
   [source,options=nowrap]
   ----
  -scheduler.kubernetes.entryPointStyle=<Entry Point Style>
  +deployer.kubernetes.entryPointStyle=<Entry Point Style>
   ----
   
   
  
positive.code: 
  ==== Environment Variables
  
  To influence the environment settings for a given application, you can take advantage of the `spring.cloud.scheduler.kubernetes.environmentVariables` property.
  For example, a common requirement in production settings is to influence the JVM memory arguments.
  You can achieve this by using the `JAVA_TOOL_OPTIONS` environment variable, as the following example shows:
  
  [source]
  ----
  scheduler.kubernetes.environmentVariables=JAVA_TOOL_OPTIONS=-Xmx1024m
  ----
  
  NOTE: When deploying stream applications or launching task applications where some of the properties may contain sensitive information, use the `shell` or `boot` as the `entryPointStyle`. This is because the `exec` (default) converts all properties to command line arguments and thus may not be secure in some environments.
  
negative.code: 
  [source,options=nowrap]
  ----
  deployer.kubernetes.imagePullPolicy=Always
  ----
  
  
  