Can it help with Kubernetes migrations?

Yes, it specifically includes patterns for investigating kOps-managed clusters to identify configurations that need consideration when migrating to EKS.

What is Infrastructure Archaeology?

It is a systematic process of investigating and documenting existing cloud infrastructure where documentation is missing, context has been lost, or systems have been inherited.

Which cloud providers does this skill support?

The skill includes specialized investigation patterns for AWS, Microsoft Azure, and Kubernetes environments, including kOps-managed clusters.

How does it handle undocumented resources during company mergers?

It identifies redundant resources, overlapping CIDR ranges, and legacy IAM trust relationships by correlating CloudTrail logs, naming patterns, and resource metadata.

What is the difference between factual and inferred documentation in this skill?

The skill follows a principle of never asserting intent; it records what exists as fact and explicitly labels assumptions about 'why' something was built as (inferred).

Infrastructure Archaeology

Name: Infrastructure Archaeology
Author: simplycycling

bysimplycycling

0•

클라우드 인프라

Investigates, interprets, and documents legacy infrastructure and configuration history to reveal the original intent behind complex technical decisions.

Infrastructure Archaeology is a specialized skill designed to help engineers navigate the complexity of inherited environments, particularly during company mergers or migrations from legacy systems like kOps to EKS. It provides systematic frameworks for mapping AWS, Azure, and Kubernetes resources, identifying redundant artifacts, and uncovering the original intent behind undocumented configurations. By moving from evidence to hypothesis, it enables teams to safely untangle technical debt and document current-state architectures with factual precision and clarity.

주요 기능

01Kubernetes cluster analysis including specialized kOps state store deep-dives

02Multi-cloud investigation patterns for AWS and Azure resource mapping

030 GitHub stars

04Standardized tagging strategies for legacy resources and technical debt identification

05Automated generation of Infrastructure Documentation and Architecture Decision Records (ADRs)

06Systematic framework for reverse-engineering configurations during company mergers

사용 사례

01Documenting inherited infrastructure after a company merger or acquisition

02Reverse-engineering complex network topologies and IAM relationships with missing documentation

03Preparing for cloud migrations from legacy tools like kOps to modern platforms like EKS

주요 기능

01Kubernetes cluster analysis including specialized kOps state store deep-dives

02Multi-cloud investigation patterns for AWS and Azure resource mapping

030 GitHub stars

04Standardized tagging strategies for legacy resources and technical debt identification

05Automated generation of Infrastructure Documentation and Architecture Decision Records (ADRs)

06Systematic framework for reverse-engineering configurations during company mergers

사용 사례

01Documenting inherited infrastructure after a company merger or acquisition

02Reverse-engineering complex network topologies and IAM relationships with missing documentation

03Preparing for cloud migrations from legacy tools like kOps to modern platforms like EKS