Fix/helm executable#7
Open
dermotmburke wants to merge 27 commits into
Open
Conversation
- Bump all module versions to 0.0.1-SNAPSHOT (required by release plugin) - Add SCM block and maven-release-plugin to root pom; release:perform runs 'deploy' with maven.deploy.skip=true so only Jib executes - Jib in each service module: install/dockerBuild -> deploy/build, targeting ghcr.io/dermotmburke/<artifact>:<version> with env-var auth - Simplify workflow to release:prepare + release:perform using GITHUB_TOKEN https://claude.ai/code/session_01Jegt4LhGbwwWa4XbeL91Hd
…lish-mmE1u Add GitHub Actions workflow to publish Jib images to ghcr.io on merge to main
Chart deploys all three app services plus Zipkin and Kafka UI inline; Kafka and Loki/Promtail/Grafana come in as Bitnami/Grafana subcharts. All services wired via release-name-prefixed service DNS names. https://claude.ai/code/session_01Jegt4LhGbwwWa4XbeL91Hd
Remove Kafka/Zipkin/Loki subcharts and inline infra deployments. Kafka bootstrap servers and Zipkin endpoint are now plain values to wire up against existing infrastructure. https://claude.ai/code/session_01Jegt4LhGbwwWa4XbeL91Hd
Inject DD_AGENT_HOST from node IP (downward API) and point MANAGEMENT_TRACING_EXPORT_ZIPKIN_ENDPOINT at the agent's Zipkin receiver. Port defaults to 9411, configurable via datadog.agentZipkinPort. https://claude.ai/code/session_01Jegt4LhGbwwWa4XbeL91Hd
After release:prepare resolves the version (read from release.properties), update chart/Chart.yaml and push the packaged chart as an OCI artifact to ghcr.io/dermotmburke alongside the container images. https://claude.ai/code/session_01Jegt4LhGbwwWa4XbeL91Hd
Replaces manual sed/helm CLI steps in the workflow with the kokuwaio
helm-maven-plugin bound to the deploy phase. Chart is versioned from
\${project.version} and pushed to oci://ghcr.io/dermotmburke alongside
the container images during release:perform.
https://claude.ai/code/session_01Jegt4LhGbwwWa4XbeL91Hd
Add Helm chart for Kubernetes deployment
Fix helm-maven-plugin version to 6.17.0
Fix: install Helm in release workflow
helm-maven-plugin can't find the helm binary when release:perform forks a subprocess. Use helm CLI directly after release:perform instead — read version from release.properties, update chart/Chart.yaml, package and push to oci://ghcr.io/dermotmburke. https://claude.ai/code/session_01Jegt4LhGbwwWa4XbeL91Hd
The plugin downloads Helm itself (useLocalHelmBinary defaults to false) but requires helmVersion to know what to fetch. Without it the binary is never downloaded and the build fails with 'Helm executable not found'. No need for setup-helm in the workflow. https://claude.ai/code/session_01Jegt4LhGbwwWa4XbeL91Hd
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.