Closed
Conversation
04bc7db to
445429d
Compare
fda104a to
472375b
Compare
478b82a to
be9db41
Compare
be9db41 to
44d0f76
Compare
d8fabe2 to
d484f7b
Compare
de0e65d to
8498b9b
Compare
0270ec1 to
2865f60
Compare
Fix test;
Changes to get 'make test' running Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> commenting out 3 of 4/5 Collect statements for debugging Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> commenting out 4 of 4/5 Collect statements for debugging Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> adding print statements and commenting out 3 of 4/5 Collect statements for debugging Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> adding more print statements Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> adding more print statements Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> adding more print statements Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> adding more print statements Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> adding more debug print statements Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> Revert "adding more debug print statements" This reverts commit eefc74f. Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> Revert "adding more print statements" This reverts commit 958fd00. Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> Revert "adding more print statements" This reverts commit 0b2d81b. Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> Revert "adding more print statements" This reverts commit a25e782. Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> Revert "adding more print statements" This reverts commit d433ce5. Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com> Adding print statements of status collect middleware to stderr Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com>
Co-authored-by: Susanne Salzmann <susanne.salzmann@sap.com>
Update spec/jobs/golangapiserver/apiserver_spec.rb Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> revert refactoring debug-> remove rate limiter atm to identify policy enpoints Revert "debug-> remove rate limiter atm to identify policy enpoints" This reverts commit f5e5c57. add test to verify health configurations enable default /actuator/health &a /actuator/promethus use standalone prometheus server for health endpoints Revert "enable default /actuator/health &a /actuator/promethus" This reverts commit 86e5523.
…metheus lib) wip:spring security wip: block health route to main server (port 8080) via spring security wip: Block health routes to main server (port 8080) using Request Filter wip: add basic auth for protected resource using servlet filter test health server configuration Adding MultiPortFilter tests finish MultiPortFilter tests
refactor: Basic and Port Filters fix java formatting issues
joergdw
requested changes
May 17, 2023
joergdw
requested changes
May 23, 2023
start health server on defined ports (Port 0 is not allowed)
…alth/liveness) to avoid breaking changes
joergdw
requested changes
May 25, 2023
| if (ObjectUtils.isEmpty(unprotectedEndpointsConfig)) { // health endpoints are authorized | ||
| isUserAuthenticatedOrSendError(chain, httpRequest, httpResponse); | ||
| } else if (!ObjectUtils.isEmpty(unprotectedEndpointsConfig)) { | ||
| Map<String, Boolean> validateMap = checkValidEndpoints(unprotectedEndpointsConfig); |
Contributor
There was a problem hiding this comment.
- I think a config-check should rather go into the config-class itself (see former comments).
- The name may be misleading. I rather understand it as a
nonExistingEndpoints. - Why do we need a boolean? Isn't pure existence enough? Then a set (as mentioned above) would be more appropriate.
Contributor
There was a problem hiding this comment.
As an additional note, when I think about what we want to do: It would simplify a lot to have a function with the following signature in the class HealthServerConfiguration:
public boolean endpointIsUnprotected(<Some type> endpoint) {…It is then reusable here! And as it will be quite performant, this simplification would then make as well obvious that we do not need the special case treatment in the lines 58-59 of the current implementation.
…ler/rest/BasicAuthenticationFilter.java Co-authored-by: joergdw <joerg.weisbarth@sap.com>
…ler/conf/HealthServerConfiguration.java Co-authored-by: joergdw <joerg.weisbarth@sap.com>
…ler/conf/HealthServerConfiguration.java Co-authored-by: joergdw <joerg.weisbarth@sap.com>
|
Kudos, SonarCloud Quality Gate passed!
|
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
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.








This change introduces new
/health/liveness endpoint, allowing users to check the health of the individual servicesThe response
{"overall_status":"UP","checks":[]}Also, the following existing endpoints are now moved to the new paths
Golang Microservices
Scheduler Microservice
By default, all health routes are protected with basic auth.
However, routes can be configured to be unprotected by using the configuration
autoscaler.apiserver.health.unprotected_endpoints