GitHub user parshimers added a comment to the discussion: Approach: unifying AWS (EKS) and on-premise Kubernetes deployment under bin/k8s — Helm-only vs eksctl vs Terraform
eksctl is just for Amazon's distribution of k8s. Which is fine, as stated GCP/Azure are way less popular, and on prem is always unique. The important thing is that there is no hard binding to AWS and that's already the case. I think having a well documented set of steps for setting up everything on AWS is a very good idea. IAM in particular is a nightmare without knowing exactly what each service actually needs. People running on prem will have their own particular setups that will need interpretation anyway. For example they probably have some object store, but each one will have it's own configurations for buckets and so on. It's not possible for us as developers to say how that's done on each system a priori. There should be guidelines (e.g. what addresses and ports the various services need, what object stores are known to work, etc.) but not specifics. Maybe an example with some particular set of services would be a good intermediate step, because then the administrator would be able to draw analogies to their environment. I have gone through Milvus's setup on AWS and that was about as straightforward as it could be. It really would have taken me a very long time to figure out things on my own without that walkthrough. GitHub link: https://github.com/apache/texera/discussions/5641#discussioncomment-17310476 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
