Skip to content

Conversation

@paigecalvert
Copy link
Contributor

No description provided.

@replicated-ci replicated-ci added type::docs Improvements or additions to documentation type::feature labels Sep 24, 2024
@netlify
Copy link

netlify bot commented Sep 24, 2024

Deploy Preview for replicated-docs ready!

Name Link
🔨 Latest commit 79beb8f
🔍 Latest deploy log https://app.netlify.com/sites/replicated-docs/deploys/66f45880e4c536000897ce7e
😎 Deploy Preview https://deploy-preview-2680--replicated-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@netlify
Copy link

netlify bot commented Sep 24, 2024

Deploy Preview for replicated-docs-upgrade ready!

Name Link
🔨 Latest commit 79beb8f
🔍 Latest deploy log https://app.netlify.com/sites/replicated-docs-upgrade/deploys/66f4588065d5360007e5c795
😎 Deploy Preview https://deploy-preview-2680--replicated-docs-upgrade.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@paigecalvert paigecalvert marked this pull request as ready for review September 25, 2024 15:47
@paigecalvert paigecalvert requested a review from a team as a code owner September 25, 2024 15:47
The `--pod-cidr` and `--service-cidr` flags are not supported on Red Hat Enterprise Linux (RHEL) 9 operating systems.
The `--pod-cidr` and `--service-cidr` flags are not supported on Red Hat Enterprise Linux (RHEL) 9 operating systems.

## Relocate Admin Console and LAM Ports
Copy link
Contributor Author

@paigecalvert paigecalvert Sep 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^ Added a new section to the Install topic. Probably gonna need more of a reference topic for all these flags soon


### Port Requirements

Embedded Cluster requires that the following ports are available:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^ Wasn't sure if it would be necessary to spell this out, but we could add something like: "Ensure that no other processes are using them and add firewall openings for these ports, unless otherwise indicated."

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could say "open and available" so that it covers something else already being bound there and the port being inaccessible due to a firewall.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this go on the EC requirements page too?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yeah meant to add a note/link to this section in the requirements partial

* The same proxy settings provided during install must be provided to the restore command using `--http-proxy`, `--https-proxy`, and `--no-proxy`.

* If the `--pod-cidr` and `--service-cidr` flags were used during install to the set IP address ranges for Pods and Services, these flags must be provided with the same CIDRs during the restore. If these flags are not provided or are provided with different CIDRs, the restore will fail with an error message telling you to rerun with the appropriate flags and values. However, it will take some time before that error occurs.
* If the `--admin-console-port` flag was used during install to relocate the Admin Console port, note that during a restore the Admin Console port will be used from the backup and cannot be changed. For more information, see [Relocate Admin Console and LAM Ports](/enterprise/installing-embedded#relocate-admin-console-and-lam-ports).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^ Added to limitations in the DR topic

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same relocate wording change here

Where `APP_SLUG` is the unique application slug.

You will be guided through the process of restoring from a backup. When prompted, enter the information for the backup storage location.
Note the following requirements for the `restore` command:
Copy link
Contributor Author

@paigecalvert paigecalvert Sep 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I noticed that we had some of this listed under "Limitations", but it felt like it would be more useful as a heads up when you are about to run the restore command (and they felt more like reqs than limitations anyway)

@paigecalvert paigecalvert requested a review from ajp-io September 25, 2024 15:51

By default, the Admin Console and Local Artifact Mirror (LAM) run on ports 30000 and 50000, respectively. If these ports are occupied, you can relocate them.

To relocate the Admin Console and LAM ports during installation with Embedded Cluster, use the `--admin-console-port` and `--local-artifact-mirror` flags with the Embedded Cluster `install` command.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And then maybe something like, "To choose different ports" or whatever.


### Limitation

It is not possible to relocate the Admin Console port during a restore with Embedded Cluster. For more information, see [Disaster Recovery for Embedded Cluster (Alpha)](/vendor/embedded-disaster-recovery).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same relocate wording change here

* The same proxy settings provided during install must be provided to the restore command using `--http-proxy`, `--https-proxy`, and `--no-proxy`.

* If the `--pod-cidr` and `--service-cidr` flags were used during install to the set IP address ranges for Pods and Services, these flags must be provided with the same CIDRs during the restore. If these flags are not provided or are provided with different CIDRs, the restore will fail with an error message telling you to rerun with the appropriate flags and values. However, it will take some time before that error occurs.
* If the `--admin-console-port` flag was used during install to relocate the Admin Console port, note that during a restore the Admin Console port will be used from the backup and cannot be changed. For more information, see [Relocate Admin Console and LAM Ports](/enterprise/installing-embedded#relocate-admin-console-and-lam-ports).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same relocate wording change here


### Port Requirements

Embedded Cluster requires that the following ports are available:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could say "open and available" so that it covers something else already being bound there and the port being inaccessible due to a firewall.

* 30000/TCP
* 50000/TCP * **

* These ports are used only by processes running on the same node. Ensure that there are no other processes using them. It is not necessary to create firewall openings for these ports.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I trust @chris-sanders knowledge and wording here, so wouldn't mind him taking a look at this one paragraph about the ports that are only bound on localhost.


### Port Requirements

Embedded Cluster requires that the following ports are available:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this go on the EC requirements page too?

paigecalvert and others added 4 commits September 25, 2024 10:32
Co-authored-by: Alex Parker <7272359+ajp-io@users.noreply.github.com>

&#42;&#42; Required for air gap installations only.

&#42;&#42;&#42; By default, the Admin Console and Local Artifact Mirror (LAM) run on ports 30000 and 50000, respectively. If these ports are occupied, you can select different ports during installation. For more information, see [Change the Admin Console and LAM Ports](/enterprise/installing-embedded#adm-lam-ports). No newline at end of file
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^ also noticed that we weren't calling out how these change be changed

* 30000/TCP &#42;&#42;&#42;
* 50000/TCP &#42; &#42;&#42; &#42;&#42;&#42;

&#42; These ports are used only by processes running on the same node. Ensure that there are no other processes using them. It is not necessary to create firewall openings for these ports.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^ @chris-sanders could you confirm that this language about the ports that need to be listening on localhost makes sense?

@@ -0,0 +1,24 @@
Embedded Cluster requires that the following ports are open and available:

* 2379/TCP &#42;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's merge this first, but just thinking out loud, I wonder if a table view here could be easier to parse. Columns like port number, protocol (tcp vs udp), local or not, air gap/online/both, etc. This might be perfectly fine too, just a thought.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that would be worth a shot!

@ajp-io ajp-io merged commit f2d9f10 into main Sep 26, 2024
5 checks passed
@ajp-io ajp-io deleted the 112535 branch September 26, 2024 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type::docs Improvements or additions to documentation type::feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants