22 lines
1002 B
Markdown
22 lines
1002 B
Markdown
|
# Roadmap
|
||
|
|
|
||
|
|
This file keeps future portfolio ideas in one place so empty folders do not look like finished work.
|
||
|
|
|
||
|
|
## Planned Lab Areas
|
||
|
|
|
||
|
|
- Docker: image build notes, container troubleshooting, and small service examples.
|
||
|
|
- Kubernetes: workload inspection, basic operations checks, and failure scenario notes.
|
||
|
|
- Terraform: small infrastructure-as-code examples with clear plan/apply separation.
|
||
|
|
- Networking: DNS, routing, firewall, and connectivity troubleshooting labs.
|
||
|
|
- CI/CD: validation pipelines for shell, YAML, and Ansible examples.
|
||
|
|
|
||
|
|
## Planned Platform Case Studies
|
||
|
|
|
||
|
|
- Storage: expansion planning, filesystem checks, and SAN handoff documentation.
|
||
|
|
- Clustering: service group checks, failover review, and operational checklists.
|
||
|
|
- Monitoring: Zabbix-oriented alert review and host onboarding notes.
|
||
|
|
- Virtualization: VM lifecycle and platform operations examples.
|
||
|
|
- Log analysis: ELK-style search examples for incident review.
|
||
|
|
|
||
|
|
Nothing in this roadmap should be read as completed implementation.
|