Channels
announcements
ask-the-community
auth
conference-talks
contribute
databricks-integration
datahub-flyte
deployment
ecosystem-unionml
engineeringlabs
events
feature-discussions
flyte-bazel
flyte-build
flyte-console
flyte-deployment
flyte-documentation
flyte-github
flyte-on-gcp
flyte-ui-ux
flytekit
flytekit-java
flytelab
great-content
hacktoberfest-2022
helsing-flyte
in-flyte-conversations
integrations
introductions
jobs
konan-integration
linkedin-flyte
random
ray-integration
ray-on-flyte
release
scipy-2022-sprint
show-and-tell
sig-large-models
torch-elastic
workflow-building-ui-proj
writing-w-sfloris
Title
f
Felix Ruess
10/14/2022, 5:11 PMHi all,
I just deployed flyte-deps (at least what I needed) and flyte-core into my small k3s cluster (metallb as external lb, traefik for ingress).
All pods seems to run fine and I can connect to the flyte console and see the deployed example projects.
But I can't seem to connect via
flytectlk
Katrina P
10/14/2022, 5:23 PMWhat's your ingress manifest look like? We had to enable grpc in traefik and then use the following rule
- kind: Rule
match: >
HostRegexp(`<HOST>`) &&
PathPrefix(`/flyteidl.{cluster:.*}`)
services:
- kind: Service
name: flyteadmin
namespace: flyte
port: grpc
scheme: h2cand then in our config for flytectl:
admin:
endpoint: dns:///<HOST>:81
insecure: true
logger:
show-source: true
level: 0f
Felix Ruess
10/14/2022, 5:33 PMthe ingress.yml is the default one from the flyte-core helm chart...
I'm new to helm and haven't quite figured out how to overwrite that one properly, if it even has proper options for this
where did you add your rule?
so I guess you are not using the
IngressIngressRoutek
Katrina P
10/14/2022, 6:30 PMI'm not using the ingress from the helm chart, you are right
And yes :
apiVersion: <http://traefik.containo.us/v1alpha1|traefik.containo.us/v1alpha1>
kind: IngressRoute
metadata:
name: flyte-routes
namespace: flyte
spec:
routes:
- kind: Rule
match: >-
HostRegexp(`<HOST>`) &&
PathPrefix(`/console`)
services:
- kind: Service
name: flyteconsole
namespace: flyte
port: httpIngressRoute is specific to traefik https://doc.traefik.io/traefik/v2.2/routing/providers/kubernetes-crd/#kind-ingressroute
f
Felix Ruess
10/14/2022, 6:32 PMdid you deploy it "manually" via plain k8s manifests, or helm or kustomize?
k
Katrina P
10/14/2022, 6:33 PMWe applied the k8s manifest without helm or kustomize (but we did use helm to generate them before we edited them)
f
Felix Ruess
10/14/2022, 6:33 PMyeah, thanks, I know the traefik CRDs
ok, will have to see if I can shoehorn that into helm somehow or if I also have to go the plain manifest route and edit them manually
did you create all the IngressRoute manifests by hand and just completely ignore the generated Ingress?
thanks for the pointers @Katrina P
there really doesn't seem to be a way to make it work with traefik v2 and
Ingress<http://traefik.ingress.kubernetes.io/service.serversscheme|traefik.ingress.kubernetes.io/service.serversscheme>Ok, only got it working by disabling the ingress creation via helm and deploying
IngressRoutenot sure what the best way would be to add this to the helm chart
k
Katrina P
10/19/2022, 12:52 AMIf you wanted to generate the manifests or chart yourself you can reference this and update it to your needs: https://github.com/flyteorg/flyte/blob/master/script/generate_helm.sh
or
helm create chart