Add ops file for enabling new CC healthchecks #1283
Conversation
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
|
We'll discuss in the upcoming ARI WG meeting on Oct 28th how to proceed with the new health check. |
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.
WHAT is this change about?
Ops file for enabling a more fine-granular health check for the cloud controller. Only applicable to the Puma webserver.
What customer problem is being addressed? Use customer persona to define the problem e.g. Alana is unable to...
Alana wants to have a reliable health monitoring for the cloud controller in peak load situations.
Please provide any contextual information.
cloudfoundry/cloud_controller_ng#4441
cloudfoundry/capi-release#560
Has a cf-deployment including this change passed cf-acceptance-tests?
Feature is tested in capi pipeline in the "gyro" experimental environment:
https://concourse.app-runtime-interfaces.ci.cloudfoundry.org/teams/capi-team/pipelines/capi/jobs/gyro-exp-tests
Does this PR introduce a breaking change? Please take a moment to read through the examples before answering the question.
How should this change be described in cf-deployment release notes?
Added ops file operations/enable-new-cc-healtchecks.yml to enable more fine-granular health check for the cloud controller running on Puma.
Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?
Does this PR make a change to an experimental or GA'd feature/component?
Please provide Acceptance Criteria for this change?
Feature is already tested in capi ci pipeline: https://concourse.app-runtime-interfaces.ci.cloudfoundry.org/teams/capi-team/pipelines/capi/jobs/gyro-exp-tests
What is the level of urgency for publishing this change?