-
Notifications
You must be signed in to change notification settings - Fork 31
feat(ec): new data directory location and configuration #2723
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
feat(ec): new data directory location and configuration #2723
Conversation
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@paigecalvert We can talk tomorrow, but we can make a few changes here:
|
|
Additionally, we could add a limitation that if you use an alternate data-dir, you must use the same location when restoring. |
| It is not possible to change the port for the Admin Console during a restore with Embedded Cluster. For more information, see [Disaster Recovery for Embedded Cluster (Alpha)](/vendor/embedded-disaster-recovery). | ||
| It is not possible to change the port for the Admin Console during a restore with Embedded Cluster. For more information, see [Disaster Recovery for Embedded Cluster (Alpha)](/vendor/embedded-disaster-recovery). | ||
|
|
||
| ## Change the Default Data Directory {#data-dir} |
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.
^ Added "Change the Default Data Directory" section in the Embedded Cluster online install topic next just below the existing section of the changing the default kotsadm/LAM ports
| ``` | ||
| Where `APP_SLUG` is the unique application slug. | ||
|
|
||
| ### Limtiations |
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.
^ Added limitations related to changing the default dir, including that you have to use the same dir during a restore
| * The filesystem at `/var/openebs` has 5Gi or more of total space | ||
| * The filesystem at `/tmp` has 5Gi or more of total space | ||
|
|
||
| * The filesystem at `/var/lib/embedded-cluster` has 40Gi or more of total space and must be less than 80% full |
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.
^ Updated the disk space requirements to clarify that you just need the embedded-cluster dir with 40gi+ of space and less than 80% full.
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.
With the change that all data is stored in the /var/lib/embedded-cluster dir, it seemed like this whole storage requirements partial could be removed. I'm thinking that if there's anything from this that we want to tell people (like some examples of what's stored in /var/lib/embedded-cluster), I could add that to the disk storage requirement
| #### `/tmp` | ||
| - Temporary space during installation | ||
|
|
||
| #### Additional Directories and Files |
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.
^ I could pull this info out of the partial and add it back to the docs. Wasn't sure if we still wanted to list these out
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.
@paigecalvert I missed this comment before. The additional list of directories would be good to add back in, just so people have a place to see places where some data is written, even if it's a lot less than is written to our data directory.
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.
Gotcha, will do
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.
Added in here: #2741
|
@emosbaugh @ajp-io this is ready for a review from you two. I think I addressed all the latest notes (and added comments to explain what I changed). |
| ### Bug Fixes {#bug-fixes-1-11-0} | ||
|
|
||
| * Fixes several issues that caused node resets to fail. Single-node clusters are no longer drained before being reset. Resets will no longer fail with the error `unable to get installation` if the installation failed early on. And node resets will now work if bind mounts are used for `/var/lib/embedded-cluster`, `/var/lib/k0s`, and `/var/openebs`. | ||
| * Fixes several issues that caused node resets to fail. Single-node clusters are no longer drained before being reset. Resets will no longer fail with the error `unable to get installation` if the installation failed early on. And node resets will now work if bind mounts are used for `/var/lib/embedded-cluster`, `/var/lib/embedded-cluster/k0s`, and `/var/lib/embedded-cluster/openebs-local`. |
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.
Do we want to retroactively change release notes? The old paths were true for this release, and moving forward we're just not mentioning the k0s and openebs directories. I don't know what's best practice here.
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.
I usually don't retroactively change release notes since they are a point-in-time representation. The exception would be if we need to pull a release or if we forgot to add something
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.
So we should undo this, right?
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.
Undid it and reapproved the PR 👍
Co-authored-by: Alex Parker <7272359+ajp-io@users.noreply.github.com>
No description provided.