I've been using eksctl whilst developing a eks/fargate deployment. During this time I have created and deleted a cluster using eksctl and a yaml file. This yaml file has not changed, so not sure why it now fails. I did clean up the aws sandbox account.

This is the panic. I happens just after it creates the fargate profile.
`panic: assignment to entry in nil map

goroutine 186 [running]:
github.com/weaveworks/eksctl/pkg/fargate/coredns.scheduleOnFargate({0x64aaf10?, 0xc00073e480?})
github.com/weaveworks/eksctl/pkg/fargate/coredns/coredns.go:122 +0xd5
github.com/weaveworks/eksctl/pkg/fargate/coredns.ScheduleOnFargate({0x64aaf10?, 0xc00073e480?})
github.com/weaveworks/eksctl/pkg/fargate/coredns/coredns.go:109 +0x27
github.com/weaveworks/eksctl/pkg/eks.ScheduleCoreDNSOnFargateIfRelevant(0xc000debe80?, 0xc000c55c50, {0x64aaf10, 0xc00073e480})
github.com/weaveworks/eksctl/pkg/eks/fargate.go:125 +0x105
github.com/weaveworks/eksctl/pkg/eks.(*fargateProfilesTask).Do(0xc0012e5800, 0x0?)
github.com/weaveworks/eksctl/pkg/eks/fargate.go:57 +0x1cc
github.com/weaveworks/eksctl/pkg/utils/tasks.doSingleTask(0x0?, {0x646e190, 0xc0012e5800})
github.com/weaveworks/eksctl/pkg/utils/tasks/tasks.go:192 +0xe6
github.com/weaveworks/eksctl/pkg/utils/tasks.doSequentialTasks(0xc000177758?, {0xc00121d5e0, 0x2, 0xc000bc27e0?})
github.com/weaveworks/eksctl/pkg/utils/tasks/tasks.go:222 +0x6a
created by github.com/weaveworks/eksctl/pkg/utils/tasks.(*TaskTree).Do
github.com/weaveworks/eksctl/pkg/utils/tasks/tasks.go:152 +0x1aa`

Can anyone advise as to what I've done wrong?