search

lacework / terraform-kubernetes-agent

A Terraform Module to create a Secret and DaemonSet for deploying the Lacework Datacollector Agent in a Kubernetes cluster.
MIT License
2 stars 16 forks source link

bug: How to update the lacework agent container with the terraform provider? #61

Closed red8888 closed 1 year ago

red8888 commented 1 year ago

Perhaps not a bug, but its not documented.

I see a manual example and a helm example, how to I pull latest image with the terraform provider correctly: https://docs.lacework.com/critical-openssl-vulnerability-linux-agent?mkt_tok=MDE2LUFUTC0yOTUAAAGH3svno-I2q403GYY9grI3Go7bb9rhw0BVw--BNidkq8Li4o3swM5hY9nRU29aJU8PthxTgIKBs5hax33MFpUre4CELMZa_5rYtqPbyaCICSZh0A#upgrade-the-lacework-linux-agent-docker-image?utm_source=marketo&utm_medium=email&utm_campaign=20221103_GLO_EMS_OpenSSL_Vulnerability

Is imagePullPolicy: Always already set by the provider? Can I just kill a pod and have it pull the "latest" tag? If imagePullPolicy: Always isn't set is it possible to set that with the terraform provider?

cirego commented 1 year ago

Hi @red8888, the current default imagePullPolicy is Always: https://github.com/lacework/terraform-kubernetes-agent/blob/aae7adb72c42f6bff223690379a08f1f8395055b/variables.tf#L48. Restarting the pod should pull the latest image, assuming that you installed with the default parameters.