Skip to content
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.

Sign up for GitHub

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

Cloud prepare doesn't open metrics ports #844

Merged
merged 2 commits into from
Oct 27, 2022
Merged

Cloud prepare doesn't open metrics ports #844

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c745101
Cloud prepare doesn't open metrics ports
vthapar Oct 27, 2022
5556f6d
Merge branch 'devel' into metrics-ports
nyechiel Oct 27, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions src/content/getting-started/_index.en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,9 +44,6 @@ For clusters behind corporate firewalls that block the default ports, Submariner
* Submariner uses UDP port 4800 to encapsulate Pod traffic from worker and master nodes to the Gateway nodes. This is required in order to
preserve the source IP addresses of the Pods. Ensure that firewall configuration allows 4800/UDP across all nodes in the cluster in both
directions. This is not a requirement when using OVN-Kubernetes CNI.
* Submariner uses TCP port 8080 to export metrics on the Gateway nodes. Ensure that firewall configuration allows ingress 8080/TCP on
the Gateway nodes so that other nodes in the cluster can access it. Also, no other workload on the Gateway nodes should be listening on TCP
port 8080.
* Worker node IPs on all connected clusters must be outside of the Pod/Service CIDR ranges.
* Submariner can be deployed on x86-64 and ARM64 nodes.
(Submariner components are deployed on _all_ nodes in the cluster,
Expand Down
4 changes: 0 additions & 4 deletions src/content/operations/deployment/subctl/_index.en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -295,7 +295,6 @@ Below is a list of available sub-commands:
| `kube-proxy-mode [flags]` | checks if the kube-proxy mode is supported by Submariner | `--namespace` `<string>`
| `cni` | checks if the detected CNI network plugin is supported by Submariner
| `firewall intra-cluster [flags]` | checks if the firewall configuration allows traffic via intra-cluster Submariner VXLAN interface | `--validation-timeout` `<value>` , `--verbose`, `--namespace` `<string>`
| `firewall metrics [flags]` | checks if the firewall configuration allows metrics to be accessed from the Gateway nodes | `--validation-timeout` `<value>` , `--verbose`, `--namespace` `<string>`
| `firewall inter-cluster <localkubeconfig> <remotekubeconfig> [flags]` | checks if the firewall configuration allows tunnels to be configured on the Gateway nodes | `--validation-timeout` `<value>`, `--verbose`, `--namespace` `<string>`
| `all` | runs all diagnostic checks (except those requiring two kubecontexts) |
<!-- markdownlint-enable line-length -->
Expand Down Expand Up @@ -387,7 +386,6 @@ This command prepares an OpenShift installer-provisioned infrastructure (IPI) on
| `--ocp-metadata` `<string>` | OCP metadata.json file (or directory containing it) to read AWS infra ID and region from
| `--profile` `<string>` | AWS profile to use for credentials
| `--region` `<string>` | AWS region
| `--metrics-ports` `<ints>` | Metrics ports, comma-separated (default 8080,8081)
| `--nat-discovery-port` `<int>` | NAT discovery port (default 4490)
| `--natt-port` `<int>` | IPsec NAT Traversal port (default 4500)
| `--vxlan-port` `<int>` | Internal VXLAN port (default 4800). Not required when using OVN-Kubernetes CNI
Expand All @@ -408,7 +406,6 @@ This command prepares an OpenShift installer-provisioned infrastructure (IPI) on
| `--ocp-metadata` `<string>` | OCP metadata.json file (or directory containing it) to read GCP infra ID and region from
| `--project-id` `<string>` | GCP project ID
| `--region` `<string>` | GCP region
| `--metrics-ports` `<ints>` | Metrics ports, comma-separated (default 8080,8081)
| `--nat-discovery-port` `<int>` | NAT discovery port (default 4490)
| `--natt-port` `<int>` | IPsec NAT Traversal port (default 4500)
| `--vxlan-port` `<int>` | Internal VXLAN port (default 4800). Not required when using OVN-Kubernetes CNI
Expand All @@ -429,7 +426,6 @@ This command prepares an OpenShift installer-provisioned infrastructure (IPI) on
| `--ocp-metadata` `<string>` | OCP metadata.json file (or directory containing it) to read OpenStack infra ID and region from
| `--project-id` `<string>` | OpenStack project ID
| `--region` `<string>` | OpenStack region
| `--metrics-ports` `<ints>` | Metrics ports, comma-separated (default 8080,8081)
| `--nat-discovery-port` `<int>` | NAT discovery port (default 4490)
| `--natt-port` `<int>` | IPsec NAT Traversal port (default 4500)
| `--vxlan-port` `<int>` | Internal VXLAN port (default 4800). Not required when using OVN-Kubernetes CNI
Expand Down
1 change: 1 addition & 0 deletions src/content/operations/usage/_index.en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,6 +79,7 @@ Pods, you can specify the `--watch` flag with the command:
$ kubectl -n submariner-operator get pods
NAME READY STATUS RESTARTS AGE
submariner-gateway-btzrq 1/1 Running 0 76s
submariner-metrics-proxy-sznnc 1/1 Running 0 76s
submariner-lighthouse-agent-586cf4899-wn747 1/1 Running 0 75s
submariner-lighthouse-coredns-c88f64f5-h77kw 1/1 Running 0 73s
submariner-lighthouse-coredns-c88f64f5-qlw4x 1/1 Running 0 73s
Expand Down