You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you follow instructions using Cognito authentication and public domain and deploy default code, you won't be able to reach JupyterHub, because in jupyterhub-values-cognito.yaml file NLB annotation is set to make NLB internal. Can you please update documentation to guide users to change that to internet-facing if they go this route. service.beta.kubernetes.io/aws-load-balancer-scheme: internal
✋ I have searched the open/closed issues and my issue is not listed.
Hi @petrokashlikov, yes, we need to update the documentation for all the blueprints. As part of our security exercise, we have shifted all internet-facing components to internal for ELB.
Could you specify which document you are referring to for JupyterHub in this case? Please post a link here.
Description
Currently if you follow instructions using Cognito authentication and public domain and deploy default code, you won't be able to reach JupyterHub, because in jupyterhub-values-cognito.yaml file NLB annotation is set to make NLB internal. Can you please update documentation to guide users to change that to internet-facing if they go this route.
service.beta.kubernetes.io/aws-load-balancer-scheme: internal
Versions
Module version [Required]: latest
Terraform version: Terraform v1.7.5
Provider version(s):
Reproduction Code [Required]
default code
Steps to reproduce the behavior:
Just follow instructions in documentation to deploy solution with Cognito authentication.
Expected behavior
JupyterHub reachable over public network
Actual behavior
JupyterHub not reachable over public network
The text was updated successfully, but these errors were encountered: