Closed mcquinne closed 1 year ago
re: item 2 - the on-prem IT team indicated that it would be easier for them moving forward to be using executable jars for all microservices (search is the only service with the war plugin installed currently, including the other API applications registry and gateway). So for now I've moved forward by revering back to only building jars.
Merging #1531 (4bbc155) into master (738d697) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## master #1531 +/- ##
=========================================
Coverage 56.13% 56.13%
Complexity 788 788
=========================================
Files 347 347
Lines 10295 10295
Branches 1167 1167
=========================================
Hits 5779 5779
Misses 4043 4043
Partials 473 473
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
PR Status:
autoscaler/v2beta2
for compatibility with current range of EKS versions (1.20-1.24+)ingressClassName
into a configurable value to avoid hard-coding3.0.0-beta2
I've verified that these changes can be deployed into EKS and that the entire system is functional.
Upon attempting the deploy the recent 3.0.0-RC4 images into a dev environment using the updated 7.17 Elastic stack, I encountered the following issues, which this branch aims to resolve:
autoscaler.enabled: true
present due to using an old HPA api versionjava -jar
with no arguments, which fails to run.