✅ Description
The goal of this activity is to align our Private Location deployments with the latest New Relic Synthetic Job Manager (SJM) release.
We have received updates indicating the availability of the latest SJM release‑549, which is also referenced in New Relic documentation. However, the corresponding Helm chart for SJM release‑549 is not currently available in the New Relic GitHub repository.
This activity includes raising a request to have the latest Helm chart published so that we can proceed with upgrading our Kubernetes based environments. This does not include performing the upgrade itself, but focuses on enabling the availability of required artifacts.
✅ Acceptance Criteria
Confirm availability of SJM release‑549 in New Relic documentation.
Validate that the Helm chart for SJM release‑549 is missing from the New Relic GitHub repository.
Raise a request for publishing the latest Helm chart version in the GitHub repository.
Ensure the Helm chart is made available and accessible for consumption.
Verify that the published Helm chart can be used for upgrading Kubernetes based Private Locations.
✅ Design Consideration/Limitations
This approach ensures that we are aligned with officially supported versions of SJM and leverage standardized deployment artifacts via Helm charts.
The limitation is that upgrades to Kubernetes based Private Locations cannot proceed until the Helm chart is made available in the GitHub repository. Additionally, any internal constraints or release cycles from the New Relic team may impact timelines.
✅ Dependencies
New Relic Synthetics team (for Helm chart release)
GitHub repository maintenance for Helm charts
New Relic documentation updates and release alignment
✅ Additional context
Kindly note that the latest SJM release‑549 is already available in New Relic documentation, but the Helm chart is not yet published in the GitHub repository.
Requesting the team to publish the latest Helm chart version at the earliest, so that we can proceed with upgrading our Private Locations to the latest SJM version and stay compliant with supported releases.
✅ Estimates
S (1–3 days)
✅ Description
The goal of this activity is to align our Private Location deployments with the latest New Relic Synthetic Job Manager (SJM) release.
We have received updates indicating the availability of the latest SJM release‑549, which is also referenced in New Relic documentation. However, the corresponding Helm chart for SJM release‑549 is not currently available in the New Relic GitHub repository.
This activity includes raising a request to have the latest Helm chart published so that we can proceed with upgrading our Kubernetes based environments. This does not include performing the upgrade itself, but focuses on enabling the availability of required artifacts.
✅ Acceptance Criteria
Confirm availability of SJM release‑549 in New Relic documentation.
Validate that the Helm chart for SJM release‑549 is missing from the New Relic GitHub repository.
Raise a request for publishing the latest Helm chart version in the GitHub repository.
Ensure the Helm chart is made available and accessible for consumption.
Verify that the published Helm chart can be used for upgrading Kubernetes based Private Locations.
✅ Design Consideration/Limitations
This approach ensures that we are aligned with officially supported versions of SJM and leverage standardized deployment artifacts via Helm charts.
The limitation is that upgrades to Kubernetes based Private Locations cannot proceed until the Helm chart is made available in the GitHub repository. Additionally, any internal constraints or release cycles from the New Relic team may impact timelines.
✅ Dependencies
New Relic Synthetics team (for Helm chart release)
GitHub repository maintenance for Helm charts
New Relic documentation updates and release alignment
✅ Additional context
Kindly note that the latest SJM release‑549 is already available in New Relic documentation, but the Helm chart is not yet published in the GitHub repository.
Requesting the team to publish the latest Helm chart version at the earliest, so that we can proceed with upgrading our Private Locations to the latest SJM version and stay compliant with supported releases.
✅ Estimates
S (1–3 days)