Skip to content

feat(java-on-amazon-eks): CON405 content from java-performance: same … #954

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ybezsonov merged 1 commit into from
Oct 13, 2026
Merged

feat(java-on-amazon-eks): CON405 content from java-performance: same … #954

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions infra/scripts/deploy/java-on-amazon-eks/ide-layout.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
#!/bin/bash
# java-on-amazon-eks runs the java-performance implementation of this step: the two workshops
# share the app, the sensor and the profiler, and one copy keeps a fix in one place. Replace
# this wrapper with an own script when the workshops diverge.
exec bash "$(dirname "${BASH_SOURCE[0]}")/../java-performance/$(basename "${BASH_SOURCE[0]}")" "$@"
5 changes: 5 additions & 0 deletions infra/scripts/deploy/java-on-amazon-eks/platform-placement.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
#!/bin/bash
# java-on-amazon-eks runs the java-performance implementation of this step: the two workshops
# share the app, the sensor and the profiler, and one copy keeps a fix in one place. Replace
# this wrapper with an own script when the workshops diverge.
exec bash "$(dirname "${BASH_SOURCE[0]}")/../java-performance/$(basename "${BASH_SOURCE[0]}")" "$@"
2 changes: 1 addition & 1 deletion infra/scripts/deploy/java-performance/platform-placement.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
#!/bin/bash
# =============================================================================
# platform-placement.sh — keep the platform off the application's node (java-performance only).
# platform-placement.sh — keep the platform off the application's node (java-performance, java-on-amazon-eks).
#
# The app selects the `workshop` NodePool (karpenter.sh/nodepool: workshop). The platform
# workloads have no selector, so Karpenter places them wherever there is room, usually on
Expand Down
9 changes: 8 additions & 1 deletion infra/scripts/templates/java-on-amazon-eks.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,13 @@
# cluster is still being created, which is the longest wait of the bootstrap.
#
# A background app-prepare (repo + :latest), prebuild fallbacks, profiler image,
# sensor image, claude-code.sh, prompt
# sensor image, claude-code.sh, IDE terminal layout, prompt
# B cluster eks.sh (waits for ACTIVE), nodepool-pin, metrics-server
# C monitoring Prometheus, Pyroscope, Grafana (shared setup/monitoring.sh)
# --- wait for A ---
# D app app-deploy (namespace, Pod Identity, manifests) } in
# E platform perf-profiler install, startup-cpu-boost, perf-sensor } parallel
# placement platform Deployments/StatefulSets → own platform NodePool
# F verify ALB answers, sensor measures, Claude wiring present
#
# Each stage script is idempotent and runnable on its own from the IDE.
Expand Down Expand Up @@ -50,6 +51,7 @@ stage "A (background): repo + images + Claude Code"
bash "$DEPLOY/perf-profiler.sh" build
bash "$DEPLOY/perf-sensor.sh" build
bash "$DEPLOY/claude-code.sh"
bash "$DEPLOY/ide-layout.sh"
# Prompt: drop vcs, kubecontext and aws segments (three terminals, less noise).
P10K="$HOME/.p10k.zsh"
if [ -f "$P10K" ]; then
Expand All @@ -63,10 +65,12 @@ A_PID=$!
stage "B: EKS cluster"
run "EKS cluster configured" "$SETUP/eks.sh"
try "NodePool pinned to m6a" "$DEPLOY/nodepool-pin.sh"
run "Platform NodePool created" "$DEPLOY/platform-placement.sh" pool
try "metrics-server installed" "$DEPLOY/metrics-server.sh"

# --- C: monitoring ---------------------------------------------------------------------
stage "C: monitoring (Prometheus, Pyroscope, Grafana)"
export MONITORING_NODEPOOL=platform # monitoring.sh installs the stack onto the platform pool
run "Monitoring stack deployed" "$SETUP/monitoring.sh"

# --- wait for A -------------------------------------------------------------------------
Expand Down Expand Up @@ -98,6 +102,9 @@ cat "$D_LOG"; cat "$E_LOG"
[ "$D_RC" -eq 0 ] && log_success "$(stamp)Stage D done (app deployed)" || { log_error "$(stamp)Stage D FAILED"; exit 1; }
[ "$E_RC" -eq 0 ] && log_success "$(stamp)Stage E done (profiler, boost, sensor)" || { log_error "$(stamp)Stage E FAILED"; exit 1; }

# --- platform placement: platform pods off the app's node ------------------------------
run "Platform on its own NodePool" "$DEPLOY/platform-placement.sh"

# --- F: verify --------------------------------------------------------------------------
stage "F: verify"
run "Environment verified" "$DEPLOY/verify.sh"
Expand Down
Loading
Loading