Kubernetes HealthChecks Operator #418
Merged
Conversation
This file contains 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
ogmaresca
reviewed
Mar 10, 2020
ogmaresca
reviewed
Mar 10, 2020
ogmaresca
reviewed
Mar 10, 2020
ogmaresca
reviewed
Mar 10, 2020
ogmaresca
reviewed
Mar 10, 2020
ogmaresca
reviewed
Mar 10, 2020
ogmaresca
reviewed
Mar 10, 2020
|
@ggmaresca , thanks for the review. Let's me address the changes |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Version 3.0.0-beta.1 of the new Kubernetes Healthchecks Operator, targetting netcoreapp3.0
Features:
[✓] New Custom resource definition (HealthChecks) (Might change in final version)
[✓] Automatic UI image deployment / removal and service deployment / removal when creating or removing healthcheck crds.
[✓] Automatic service discovery, removal and updates using a push model instead of the current UI
pull model. The operator will listen to configured labels in CRD definition and this can be overriden
with labels configured in services.
[✓] Automatic UI push endpoint exposure protected by an api key stored and created as a secret by kubernetes operator
Notes:
The UI Collector has been updated to support updated paths and schemes and reflect the execution histories properly. This was not supported before and now it can be updated by the operator
The push endpoint can only be enabled by setting the proper configuration and the api key secret is only known by the operator that retrieves the value from a namespaced secret