Helm can't handle ConfigMap.mapRoles.username : system:node:{{EC2PrivateDNSName}}

user_9345860 0
Viewed 1072

I have a kubernetes cluster that I'm now migrating to Helm. Cluster is running under AWS managed service AWS EKS.

Since AWS EKS by default creates only 1 user in the cluster (system.master) which is the AWS User who created the cluster. Having said that, in order to create another user to the cluster, I wound need to create a config map below:

apiVersion: v1
kind: ConfigMap
metadata:
  name: aws-auth
  namespace: kube-system
data:
  mapRoles: |
    - rolearn: arn:aws:iam::<accountid>:role/terraform-eks-main-node
      username: system:node:{{EC2PrivateDNSName}}
      groups:
        - system:bootstrappers
        - system:nodes
  mapUsers: | 
    - userarn: arn:aws:iam::<accountid>:user/admin-access 
      username: admin-access 
      groups: 
        - system:masters

running the configmap using helm causes issues due to {{EC2PrivateDNSName}}. Is there any proper way to handle it?

amazon-eks kubernetes-helm kubernetes amazon-web-services
1 Answers

Whenever Helm (and the embedded Go text/template engine) sees {{, it interprets it as a template variable expansion. If you want to include those characters literally in the output, you need a template expression that generates them; for example

username: system:node:{{ "{{" }}EC2PrivateDNSName}}
user_100081730
Related