Felix Ruess
10/14/2022, 5:11 PMflytectl
, which seems to try to connect via gRPC?
Any pointers?Katrina P
10/14/2022, 5:23 PM- kind: Rule
match: >
HostRegexp(`<HOST>`) &&
PathPrefix(`/flyteidl.{cluster:.*}`)
services:
- kind: Service
name: flyteadmin
namespace: flyte
port: grpc
scheme: h2c
admin:
endpoint: dns:///<HOST>:81
insecure: true
logger:
show-source: true
level: 0
Felix Ruess
10/14/2022, 5:33 PMIngress
from the helm chart, but deployed your own traefik specific IngressRoute
where you can specify that rule?Katrina P
10/14/2022, 6:30 PMapiVersion: <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: http
Felix Ruess
10/14/2022, 6:32 PMKatrina P
10/14/2022, 6:33 PMFelix Ruess
10/14/2022, 6:33 PMIngress
as you can't seem to specify the protocol (e.g. via <http://traefik.ingress.kubernetes.io/service.serversscheme|traefik.ingress.kubernetes.io/service.serversscheme>
as an ingress annotation, only in a service annotation (and then it applies to all ports of the service... which would mean a major refactoring of the flyteadmin manifests/helm templatesIngressRoute
manually, and then using port 80:Katrina P
10/19/2022, 12:52 AMhelm create chart
from
https://github.com/flyteorg/flyte/tree/master/charts and update /delete what you need from the templates (could use .helmignore maybe to ignore the templates you don't want to include)