-
Notifications
You must be signed in to change notification settings - Fork 1
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
Configure firewall rules #46
Conversation
- Other VMs SSHD: `22` | ||
|
||
Audit: | ||
Gateway VM: |
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.
Grouping by VM might be more helpful for looking up opening ports.
The infra diagram can be used to look up available services
- cAdvisor: `8088` | ||
- Node Exporter: `9100` | ||
- ContainerSSH auth-config server: `8080` | ||
- ContainerSSH metrics server(TBD): `9101` |
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.
will be done in #45
- SSH: `2333` | ||
- cAdvisor: `8088` | ||
- Node Exporter: `9100` | ||
- ContainerSSH auth-config server: `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.
removed auth-config
from the infra diagram since it might be not very important to our project.
@@ -62,7 +62,7 @@ resource "google_compute_instance" "sacrificial_vm" { | |||
resource "google_compute_instance" "logger_vm" { | |||
name = "logger-vm" | |||
machine_type = var.machine_type | |||
tags = ["observer"] | |||
tags = ["logger"] |
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.
might be easier to identify
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.
yes, it makes sense, sorry for my bad naming sense xD
# open gateway-port 9100 and 9101, to our prometheus and metrics server | ||
resource "google_compute_firewall" "firewall_gateway_nodeexport" { | ||
name = "firewall-gateway-nodeexport" | ||
resource "google_compute_firewall" "allow_all_to_logger_vm_prometheus" { |
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.
still need it for testing metrics server later later.
could close it later
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.
ok, i need it as well ^^v
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.
LGTM. :)
Description
This PR will
action_source_to_destination_service/port
Testing the PR
terraform apply
Takeaways
So we don't need to allow both ways for a connection.