Feature Request: Provide documentation and templates for kubernetes deployments
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- grafana, helm, kubernetes, prometheus
- Domain
- devops, infrastructure, observability-sre
Research direction
Review the existing Docker Compose deployment and AST telemetry configuration first, then determine how the requested Kubernetes workflows should be scoped. Done would require documented Kubernetes templates or Helm charts, inventory-driven collector scaling, and Kubernetes secret integration with password rotation support; the issue does not name specific files or tests.
Written by the indexing model from the issue text.
Description
Background
After F5 customers test AST with docker compose in the lab, there is then an effort they must undergo to retrofit AST for production deployments to collect metrics from dozens, hundreds, potentially thousands of Big-IPs.
To accelerate production deployments at scale, it would be helpful for AST project to provide Kubernetes documentation and templates to run AST in a container orchestration platform.
Example things that would be helpful:
- Full stack otel collector + grafana + prometheus deployment in Kubernetes via Helm chart
- Minimal Otel collector deployment in Kubernetes via Helm chart.
- With documentation to incorporate with existing Grafana/Prometheus.
- Ability to define single list of all F5 inventory to be monitored and then dynamically create n-number otel collectors to handle the inventory list.
- Secrets integration with Kubernetes
- including rotating Big-IP passwords used by otel collectors when Big-IP passwords are updated.
- Dominant language
- Python
- Stars
- 106
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from f5devcentral/application-study-tool
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
f5devcentral/application-study-tool#267 · 7 comments ·
All issues in f5devcentral/application-study-tool
Similar issues
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31098 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
john-kurkowski/tldextract#382 ·
-
comp/tools duplicate P2 sweeper:risk-compatibility tool/mcp type/bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
NousResearch/hermes-agent#132042 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
deepset-ai/haystack#13092 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
feder-cr/invisible_playwright_mcp#1408 ·
Maintainers usually reply within 1 day