FeatureHub EDGE API failing inside of Kubernetes Cluster with HTTP 400 Bad Request when accessing MR Admin website

[thedanchez]

Summary

I'm trying to self-host FeatureHub in my org's K8s cluster and the EDGE API pod is failing with a HTTP 400 when I attempt to access the FeatureHub Management Repo Admin host/path in my browser.

The stack trace is the following:

jakarta.ws.rs.BadRequestException: HTTP 400 Bad Request
io.featurehub.edge.rest.FeatureGetProcessor.processGet(FeatureGet.kt:58) ~[edge-common-1.1-SNAPSHOT.jar:?]
io.featurehub.edge.rest.EventStreamResource.getFeatureStates(EventStreamResource.java:57) ~[edge-full-1.1-SNAPSHOT.jar:?]
jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:52) ~[jersey-server-3.0.3.jar:?]
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:124) ~[jersey-server-3.0.3.jar:?]
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:167) ~[jersey-server-3.0.3.jar:?]
org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$VoidOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:159) ~[jersey-server-3.0.3.jar:?]
org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:79) ~[jersey-server-3.0.3.jar:?]
org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:475) ~[jersey-server-3.0.3.jar:?]
org.glassfish.jersey.server.model.ResourceMethodInvoker.lambda$apply$0(ResourceMethodInvoker.java:387) ~[jersey-server-3.0.3.jar:?]
org.glassfish.jersey.server.ServerRuntime$AsyncResponder$2$1.run(ServerRuntime.java:816) [jersey-server-3.0.3.jar:?]
org.glassfish.jersey.internal.Errors$1.call(Errors.java:248) [jersey-common-3.0.3.jar:?]
org.glassfish.jersey.internal.Errors$1.call(Errors.java:244) [jersey-common-3.0.3.jar:?]
org.glassfish.jersey.internal.Errors.process(Errors.java:292) [jersey-common-3.0.3.jar:?]
org.glassfish.jersey.internal.Errors.process(Errors.java:274) [jersey-common-3.0.3.jar:?]
org.glassfish.jersey.internal.Errors.process(Errors.java:244) [jersey-common-3.0.3.jar:?]
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:265) [jersey-common-3.0.3.jar:?]
org.glassfish.jersey.server.ServerRuntime$AsyncResponder$2.run(ServerRuntime.java:811) [jersey-server-3.0.3.jar:?]
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?]
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?]
java.lang.Thread.run(Thread.java:829) [?:?]

The JSON error payload (minus the stack_trace field since I posted the value above) is the following:

{
  "@timestamp": "2022-04-22T15:19:46.682+0000",
  "message": "Failed jersey request",
  "priority": "ERROR",
  "path": "io.featurehub.jersey.config.LocalExceptionMapper",
  "thread": "jersey-server-managed-async-executor-0",
  "host": "featurehub-edge-68cb97969f-58pt6"
}

Not sure what is going on here but could use some direction.

Additional Details

• FeatureHub version 1.5.7

[rvowles]

Hi there, can you tell us a bit more? Are you installing using the sample k8s chart we provide in featurehub-installs or your own? The implication from the log you have provided is that Edge is being deployed separately? That specific line of code is triggering when it does not detect any API keys are being passed on a GET request, so a 400 indicates its an invalid request because nothing is being asked for, could you give us an idea of the URL construct you are using? Thanks!