-
Notifications
You must be signed in to change notification settings - Fork 0
add ingress cidr block to improve security #117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
jubrad
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approve with one comment
| #### Console Access | ||
| The Materialize Console is available on port 8080. For security, we recommend accessing it via Kubernetes port-forwarding rather than exposing it publicly if possible, though it is available on the NLB through sql access. | ||
|
|
||
| **Via Port Forwarding:** | ||
| ```bash | ||
| # Forward local port 8080 to the Materialize service | ||
| kubectl port-forward svc/mz<resource-id>-console 8080:8080 -n materialize-environment | ||
| ``` | ||
| Then open your browser to `http://localhost:8080`. | ||
|
|
||
| --- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on the code the console should also be available on the public NLB we should split up the docs here to say if public use public access if private port forward for both console and sql
| locals { | ||
| trimmed_name_prefix = substr(var.name_prefix, 0, min(6, length(var.name_prefix))) | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need a comment about why we're trimming
#113