https://flyte.org
Join Slack
```vendor.4cb66fb8bb2bca222104.js:8 Error: invalid wire type 4 at offset 1 at l.skipType (vendor...
# flyte-support
a
Copy code
vendor.4cb66fb8bb2bca222104.js:8 Error: invalid wire type 4 at offset 1
    at l.skipType (vendor.4cb66fb8bb2bca222104.js:2:33214)
    at e.decode (vendor.4cb66fb8bb2bca222104.js:8:1795729)
    at t.decodeProtoResponse (main.31219686ea86aafa4419.js:1:541961)
    at t.getAdminEntity (main.31219686ea86aafa4419.js:1:539552)
receving this error in the browsers console...
h
Hey @able-oxygen-76238 sorry you are having an issue... have you installed flyte-binary? or flyte-core? helm charts? or is this 
flytectl demo start
?
a
flyte-binary
helm charts
h
oh... do you happen to know which version?
a
latest
h
That's not good 🙂 @high-accountant-32689 mind taking a look? This looks like a proto incompatibility issue?
a
@high-park-82026 let me give you more clarity I'm deploying flyte with my existing application I did changes in dockerfile of flyteconsole for base url and admin API url Also did changes in go conde change hard-coded /console to mine route
Also I'm using /flyte instead of /console and for admin API url also using /flyte
As a prefix
So my existing route will not conflict
h
@able-oxygen-76238, can you share which exact changes you made?
a
in https://github.com/flyteorg/flyteconsole/blob/master/Dockerfile RUN : \ --mount=type=cache,target=/root/.yarn \ # install production dependencies && yarn workspaces focus --all --production \ && yarn build:types \ && BASE_URL=/flyte ADMIN_API_URL=/flyte yarn run build:prod \ && mkdir /app \ && cp -R ./website/dist/* /app
these are two changes i made
@high-park-82026
h
ok, thanks. Looking.
a
ingress.yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: flyte-binary spec: ingressClassName: beta rules: - http: paths: - path: /flyte pathType: Prefix backend: service: name: flyte-binary-http port: number: 8088
h
@able-oxygen-76238, why are you setting 
ADMIN_API_URL
to 
/flyte
?
a
Yes
becasue /api is making conflct with my existing app
also api sending wrong response
@high-park-82026
h
@able-oxygen-76238, from the screenshot you pasted the call to 
/flyte/api/v1/projects
is returning the flyteconsole main page. Let me take another look at how we route requests in single-binary.
t
@able-oxygen-76238 could take a step back and help me understand what you’re trying to do? like ultimately what’s the goal?
f
@able-oxygen-76238 this is not really a supported pattern and better not to do it
the snowflake solutions are very hard to maintain
a
@thankful-minister-83577 let me give you more clarity I'm deploying flyte with my existing application I did changes in dockerfile of flyteconsole for base url and admin API url Also did changes in go conde change hard-coded /console to mine route so the main goal is I want to configure flyte-binary to not to clash with my existing routes
Hey can you do me a favor I setup the things for flyte it's working as per my requirements Just I need to flytectl config init I'm just using http service and I also have an ingress for the same How can I use http ingress or service.
h
flytectl expect grpc... did you configure that as well?
36 Views
Open in Slack
PreviousNext
Powered by

Flyte

Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Powered by