(Optional) Running Amazon AppConfig as a DaemonSet in Amazon EKS
With Amazon EKS, you can run Amazon AppConfig Agent as a sidecar, which results in one agent
container per application pod. Or, if you prefer, you can run Amazon AppConfig
Agent as a DaemonSet
Note
If you run Amazon AppConfig Agent as a DaemonSet, the agent runs in a separate pod, which
means you can't access it with calls to localhost. You must inject or
otherwise discover the agent pod's IP address in order to call it.
To run Amazon AppConfig Agent as a DaemonSet, create a manifest file with the following
contents. Replace highlighted text with details for your
application and environment. For Amazon Web Services Region, specify an
Amazon Web Services Region code (for example, us-west-1).
apiVersion: apps/v1 kind: DaemonSet metadata: name: aws-appconfig-agent namespace:my_namespacelabels: app:my_application_labelspec: selector: matchLabels: app:my_application_labeltemplate: metadata: labels: app:my_application_labelspec: containers: - name: aws-appconfig-agent image: public.ecr.aws/aws-appconfig/aws-appconfig-agent:2.x ports: - name: http containerPort: 2772 protocol: TCP env: - name: SERVICE_REGION value:Amazon Web Services RegionimagePullPolicy: IfNotPresent # set a high priority class to ensure the agent is running on every node priorityClassName: system-node-critical
Run the following command to apply the Amazon AppConfig Agent DaemonSet to your cluster. Replace
aws_appconfig_agent_daemonset with the name of your DaemonSet
manifest.
kubectl apply -faws_appconfig_agent_daemonset.yml