Skip to content

Update directory structure per cloud provider and main readme #74

@runatyr1

Description

@runatyr1

The project has two main implementations one per cloud provider: Hetzner and AWS. Initially there was only Hetzner and later on added AWS. There should be two main folders, one for each provider and every folder related to each provider should be in the corresponding folder. This involves mostly refactoring path references.

Also consider separating each provider in it's own project, although this would conflict with the git history.

AWS uses this directories so it is already more contained:
infrastructure/aws-eks
kubernetes-aws-eks

Hetzner uses all the other top level directories so it needs more refactoring:
docs
infrastructure/hetzner
infrastructure/keys
infrastructure/logs
kubernetes
scripts
vault

This is probably the best solution for the top level dirs, to allow both providers to coexist while keeping the project organized:

  • infra-aws-eks-terraform (mostly done, just need to move infrastructure/aws-eks)

  • infra-hetzer-terraform (need to move/rename infrastructure/hetzner, infrastructure/keys, infrastructure/logs, scripts, vault)

  • kubernetes-aws-eks (already done)

  • kubernetes-hetzner (rename kubernetes)

This would facilitate working in multi cloud setups within the same project in the future, eg. adding azure, or adding other demos in aws called infra-aws-lambda, infra-aws-.. or even using other IaC like Pulumi and call it infra-aws-eks-pulumi while re-using the same kubernetes-aws-eks that was used for terraform in Pulumi.

Tasks

  • Change directory structure
  • Update main readme with the current status of the infra, with separation between cloud providers

Metadata

Metadata

Assignees

No one assigned

    Labels

    AWSAmazon Web ServicesHetznerHetzner cloud provider

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions