Pod not supported on Fargate: fields not supported: HostNetwork, port contains HostIP or HostPort

[mostafafarzaneh]

/kind bug

What happened? Our EKS cluster runs only on Fargate and when I add these lines:

  enable_aws_efs_csi_driver = true
  aws_efs_csi_driver = {
     regionalStsEndpoints = true
  }

I got the following error: Pod not supported on Fargate: fields not supported: HostNetwork, port contains HostIP or HostPort

I read that if you are using Fargate you do not need the controller. But if I do not deploy the controller, then on creating PVC, I get the following error:

0s          Warning   FailedAttachVolume   Pod/apigw-control-plane-5fd6c94569-wt2w6    AttachVolume.Attach failed for volume "apigw-cnt-pv" : timed out waiting for external-attacher of efs.csi.aws.com CSI driver to attach volume fs-04261bafa10da96c8
0s          Warning   FailedMount          Pod/apigw-control-plane-5fd6c94569-wt2w6    Unable to attach or mount volumes: unmounted volumes=[persistent-storage], unattached volumes=[persistent-storage], failed to process volumes=[]: timed out waiting for the condition

What you expected to happen? If there is no need for CSI driver for Fargate, then we should be able to create PVC successfully.

How to reproduce it (as minimally and precisely as possible)? Create an EKS with Fargate only and add CSI driver to it. Then create a PVC.

Anything else we need to know?:

Environment

• Kubernetes version (use kubectl version):
• Client Version: v1.28.3 Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3 Server Version: v1.27.6-eks-f8587cb
• Driver version: helm-chart-aws-efs-csi-driver-2.4.8

Please also attach debug logs to help us better diagnose

• Instructions to gather debug logs can be found here

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.