<p>Yep this worked, or at least I didn't get an error</p>
<pre><code>    $ eksctl create cluster --alb-ingress-access -f config.yaml
</code></pre>

CC BY-SA 4.0
2021-02-19T20:07:15.023Z
2021-02-19T20:07:15.023Z
Chris F
<p>You can use the <code>iam</code> key in your node groups.</p>
<pre><code>    iam:
      withAddonPolicies:
        albIngress: true
</code></pre>
<p>See an example here: <a href="https://github.com/eksctl-io/eksctl/blob/v0.149.0/examples/23-kubeflow-spot-instance.yaml#L57" rel="nofollow noreferrer">23-kubeflow-spot-instance.yaml</a></p>

CC BY-SA 4.0
2023-07-18T17:38:32.397Z
2023-07-18T17:38:32.397Z
russau
<p>I read <a href="https://www.learnaws.org/2019/12/16/running-eks-on-aws-fargate/" rel="nofollow noreferrer">How to run Serverless Kubernetes: AWS EKS on Fargate</a>, and am wondering what the equivalent option for <code>--alb-ingress-access</code> is in a config schema shown in <a href="https://eksctl.io/usage/schema/#managedNodeGroups-iam-withAddonPolicies-albIngress" rel="nofollow noreferrer">Config file schema</a>? At least it's not obvious to me. I even created a sample cluster and printed out the info and didn't see it there.</p>
<pre><code>$ eksctl create cluster \
    --name ingress-sample \
    --version 1.19 \
    --region us-east-1 \
    --fargate \
    --alb-ingress-access
$ eksctl get cluster --name ingress-sample -o yaml
- Arn: arn:aws:eks:us-east-1:0123456789:cluster/ingress-sample
  CertificateAuthority:
    Data: &lt;redacted&gt;
  ClientRequestToken: null
  CreatedAt: &quot;2021-02-19T00:44:27.976Z&quot;
  EncryptionConfig: null
  Endpoint: https://&lt;redacted&gt;.gr7.us-east-1.eks.amazonaws.com
  Identity:
    Oidc:
      Issuer: https://oidc.eks.us-east-1.amazonaws.com/id/redacted
  KubernetesNetworkConfig:
    ServiceIpv4Cidr: 10.100.0.0/16
  Logging:
    ClusterLogging:
    - Enabled: false
      Types:
      - api
      - audit
      - authenticator
      - controllerManager
      - scheduler
  Name: ingress-sample
  PlatformVersion: eks.1
  ResourcesVpcConfig:
    ClusterSecurityGroupId: sg-xxxxxx
    EndpointPrivateAccess: false
    EndpointPublicAccess: true
    PublicAccessCidrs:
    - 0.0.0.0/0
    SecurityGroupIds:
    - sg-xxxxxx
    SubnetIds:
    - subnet-111111
    - subnet-222222
    - subnet-333333
    - subnet-444444
    VpcId: vpc-xxxxxx
  RoleArn: arn:aws:iam::0123456789:role/eksctl-ingress-sample-cluster-ServiceRole-D0X7QCIRBSDN
  Status: ACTIVE
  Tags: {}
  Version: &quot;1.19&quot;
</code></pre>
<p><strong>UPDATE</strong>: Hmmm, maybe</p>
<pre><code>$ eksctl create cluster --alb-ingress-access -f config.yaml
</code></pre>

<kubernetes>
What is the equivalent of eksctl option "--alb-ingress-access" in a config file?
Chris F
# What is the equivalent of eksctl option "--alb-ingress-access" in a config file?

(Asked by: username_0 on 2021-02-19)

I read How to run Serverless Kubernetes: AWS EKS on Fargate, and am wondering what the equivalent option for --alb-ingress-access is in a config schema shown in Config file schema? At least it's not obvious to me. I even created a sample cluster and printed out the info and didn't see it there.
$ eksctl create cluster \
    --name ingress-sample \
    --version 1.19 \
    --region us-east-1 \
    --fargate \
    --alb-ingress-access
$ eksctl get cluster --name ingress-sample -o yaml
- Arn: arn:aws:eks:us-east-1:0123456789:cluster/ingress-sample
  CertificateAuthority:
    Data: 
  ClientRequestToken: null
  CreatedAt: "2021-02-19T00:44:27.976Z"
  EncryptionConfig: null
  Endpoint: https://.gr7.us-east-1.eks.amazonaws.com
  Identity:
    Oidc:
      Issuer: https://oidc.eks.us-east-1.amazonaws.com/id/redacted
  KubernetesNetworkConfig:
    ServiceIpv4Cidr: 10.100.0.0/16
  Logging:
    ClusterLogging:
    - Enabled: false
      Types:
      - api
      - audit
      - authenticator
      - controllerManager
      - scheduler
  Name: ingress-sample
  PlatformVersion: eks.1
  ResourcesVpcConfig:
    ClusterSecurityGroupId: sg-xxxxxx
    EndpointPrivateAccess: false
    EndpointPublicAccess: true
    PublicAccessCidrs:
    - 0.0.0.0/0
    SecurityGroupIds:
    - sg-xxxxxx
    SubnetIds:
    - subnet-111111
    - subnet-222222
    - subnet-333333
    - subnet-444444
    VpcId: vpc-xxxxxx
  RoleArn: arn:aws:iam::0123456789:role/eksctl-ingress-sample-cluster-ServiceRole-D0X7QCIRBSDN
  Status: ACTIVE
  Tags: {}
  Version: "1.19"

UPDATE: Hmmm, maybe
$ eksctl create cluster --alb-ingress-access -f config.yaml

**Tags:** kubernetes


---

## 2 answers

### Answer by username_0 on 2021-02-19. Score: 2 | Accepted answer

Yep this worked, or at least I didn't get an error
    $ eksctl create cluster --alb-ingress-access -f config.yaml


---

### Answer by username_1 on 2023-07-18. Score: 0

You can use the iam key in your node groups.
    iam:
      withAddonPolicies:
        albIngress: true

See an example here: 23-kubeflow-spot-instance.yaml


---

