hallowed-dog-74273
01/18/2024, 12:18 AMaverage-finland-92144
01/18/2024, 2:52 PMhallowed-dog-74273
01/18/2024, 9:22 PMhallowed-dog-74273
01/18/2024, 9:22 PMhallowed-dog-74273
01/18/2024, 9:23 PMkubectl -n flyte port-forward service/flyteadmin 8088:80 8089:81
I can forward the admin ports
kubectl -n flyte port-forward service/flyteconsole 8080:80
i can forward the web console porthallowed-dog-74273
01/18/2024, 9:24 PM<http://localhost:8080/api/v1/projects>
which is 404hallowed-dog-74273
01/18/2024, 9:24 PM<http://localhost:8088/api/v1/projects>
average-finland-92144
01/18/2024, 9:38 PMkubectl get svc -n flyte
also with this
you're forwarding the remote 80 port to 8080 locallyCopy codekubectl -n flyte port-forward service/flyteconsole 8080:80
hallowed-dog-74273
01/18/2024, 9:43 PMhallowed-dog-74273
01/18/2024, 9:43 PMhallowed-dog-74273
01/18/2024, 9:48 PMaverage-finland-92144
01/18/2024, 9:58 PMhallowed-dog-74273
01/18/2024, 10:03 PMaverage-finland-92144
01/18/2024, 10:04 PMhallowed-dog-74273
01/18/2024, 10:09 PMhallowed-dog-74273
01/18/2024, 10:10 PMaverage-finland-92144
01/18/2024, 10:12 PMhallowed-dog-74273
01/18/2024, 10:16 PMhallowed-dog-74273
01/18/2024, 10:17 PMaverage-finland-92144
01/18/2024, 10:18 PMflyte-core
chart should work
https://docs.flyte.org/en/latest/deployment/configuration/auth_setup.html#identity-management-layer-oidchallowed-dog-74273
01/19/2024, 6:46 PMhallowed-dog-74273
01/19/2024, 6:50 PMhallowed-dog-74273
01/19/2024, 6:51 PMError: Connection Info: [Endpoint: dns:///flyte.example.com, InsecureConnection?: true, AuthMode: ClientSecret]: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: http2: frame too large"
{"json":{},"level":"error","msg":"Connection Info: [Endpoint: dns:///flyte.example.com, InsecureConnection?: true, AuthMode: ClientSecret]: rpc error: code = Unavailable desc = connection error: desc = \"error reading server preface: http2: frame too large\"","ts":"2024-01-19T10:47:45-08:00"}
I have <http://flyte.example.com|flyte.example.com>
set in my /etct/hosts to the ip address of the ingress controller,average-finland-92144
01/19/2024, 7:17 PMconfig.yaml
?hallowed-dog-74273
01/19/2024, 7:21 PMadmin:
# For GRPC endpoints you might want to use dns:///flyte.myexample.com
endpoint: <dns://flyte.example.com>
insecure: true
insecureSkipVerify: true
average-finland-92144
01/19/2024, 7:23 PMinsecureSkipVerify: false
to start with pleasehallowed-dog-74273
01/19/2024, 7:25 PMhallowed-dog-74273
01/19/2024, 7:31 PMhallowed-dog-74273
01/19/2024, 7:51 PMserver {
server_name _ ;
listen 80 default_server reuseport backlog=1024 ;
listen 443 default_server reuseport backlog=1024 ssl http2 ;
so i have to enable tlshallowed-dog-74273
01/19/2024, 8:09 PMinsecureSkipVerify: true
average-finland-92144
01/19/2024, 8:13 PMadventurous-napkin-36518
03/05/2024, 3:49 PMadventurous-napkin-36518
03/05/2024, 3:50 PMaverage-finland-92144
03/05/2024, 3:52 PM$HOME/.flyte/config.yaml
Also the output of kubectl describe ingress flyte-core -n flyte
adventurous-napkin-36518
03/05/2024, 3:56 PMaverage-finland-92144
03/05/2024, 4:02 PMaverage-finland-92144
03/05/2024, 4:03 PMadventurous-napkin-36518
03/05/2024, 4:07 PMadventurous-napkin-36518
03/05/2024, 4:07 PMadventurous-napkin-36518
03/05/2024, 4:08 PMaverage-finland-92144
03/05/2024, 4:09 PM/console
to the hostname, right?adventurous-napkin-36518
03/05/2024, 4:10 PMadventurous-napkin-36518
03/05/2024, 4:11 PMadventurous-napkin-36518
03/05/2024, 4:37 PMaverage-finland-92144
03/05/2024, 4:43 PMkubectl get po -n flyte
adventurous-napkin-36518
03/05/2024, 4:43 PMaverage-finland-92144
03/05/2024, 4:44 PMadventurous-napkin-36518
03/05/2024, 4:50 PMadventurous-napkin-36518
03/05/2024, 4:50 PM