annotations: When a tracked configMap/ secret is updated, this strategy attaches a /last-reloaded-from pod template annotation.Note: This is the default reload strategy. This strategy can be specified with the -reload-strategy=env-vars argument. Referencing the changed configMap or secret on the owning resource (e.g., Deployment, StatefulSet, etc.). env-vars: When a tracked configMap/ secret is updated, this strategy attaches a Reloader specific environment variable to any containers.Reloader supports multiple "reload" strategies for performing rolling upgrades to resources. you can configure the "reload strategy" with the -reload-strategy= option (details below).you can configure logging in JSON format with the -log-format=json option.you may want to prevent watching certain resources with the -resources-to-ignore flag.you may want to prevent watching certain namespaces with the -namespaces-to-ignore flag.you may override the secret annotation with the -secret-annotation flag.you may override the configmap annotation with the -configmap-annotation flag.you may override the search annotation with the -auto-search-annotation flagĪnd the match annotation with the -search-match-annotation flag.you may override the auto annotation with the -auto-annotation flag./reload or /reload annotation will reload the pod upon changes in specified configmap or secret, irrespective of the usage of configmap or secret./auto: "true" will only reload the pod, if the configmap or secret is used (as a volume mount or as an env) in DeploymentConfigs/Deployment/Daemonsets/Statefulsets.
Here are the steps to use sealed-secrets with reloader. Reloader also supports sealed-secrets.reload: "foo-secret,bar-secret,baz-secret " spec: Then add this annotation to main metadata of your Deployment
Re loader windows all version upgrade#
To perform rolling upgrade when change happens only on specific configmaps use below annotation.įor a Deployment called foo have a ConfigMap called foo-configmap. To do this either set the auto annotation to "false" ( /auto: "false") or remove it altogether, and use annotations mentioned here or here Configmap We can also specify a specific configmap or secret which would trigger rolling upgrade only upon change in our specified configmap or secret, this way, it will not trigger rolling upgrade upon changes in all configmaps or secrets used in a deploymentconfig, deployment, daemonset, statefulset or rollout. Of whether they have the /match: "true" annotation or Will always restart upon a change in configmaps or secrets it uses, regardless auto: "true" annotation on your deployment, then it Provided the secret/configmap is being used in an environment variable, or a
0 kommentar(er)
