eve-k: Enable local-path storage for CLUSTER_TYPE_K3S_BASE#5622
Conversation
eb06b7d to
9eb6b78
Compare
|
Rebased on latest master |
9eb6b78 to
5f632b0
Compare
|
Added some details in docs/EVE-K.md under "Modes" and "User Volumes - Default PVC Options" headings. |
5f632b0 to
57b0211
Compare
|
Latest push to resolve yetus on docs/EVE-K.md. Looks like the eve scanner had issues running: Error: 2-23 16:01:10] [ERROR] Failed to get cvss-bt download URL |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5622 +/- ##
==========================================
+ Coverage 19.52% 29.49% +9.96%
==========================================
Files 19 18 -1
Lines 3021 2417 -604
==========================================
+ Hits 590 713 +123
+ Misses 2310 1552 -758
- Partials 121 152 +31 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Converted back to draft to resolve cdi upload scratch volumes using local-path |
57b0211 to
5c5c22d
Compare
5c5c22d to
99172ce
Compare
Some K3S_BASE mode use cases require local-path storage, for simplicity just enable it for all modes. Single node and CLUSTER_TYPE_REPLICATED_STORAGE continue to define all PVCs as longhorn. CLUSTER_TYPE_K3S_BASE will now allow for local volumes. Local-path storage is configured in the k3s config.yaml base config file to place all volumes in /persist/vault/volumes by default. Signed-off-by: Andrew Durbin <andrewd@zededa.com>
99172ce to
f787142
Compare
|
Issues running CVE PR Gate: |
|
/rerun red |
| The available default storage classes will vary depending on the mode which eve-k is | ||
| running as. All storage classes installed by EVE will place volumes in /persist/vault/volumes/... by default. | ||
|
|
||
| - Default single node 'First-Boot' Mode (No EdgeNodeCluster eve-api config): Longhorn and Local-Path |
There was a problem hiding this comment.
Is there a possibility for a race if the project auto-deploys applications such that the first time the device is fetching the EdgeNodeConfig from the controller it receives both a set of applications to download and deploy, and in the same config receives EdgeNodeCluster.ClusterType? That means it might need to change the CLUSTER_TYPE while it is downloading to /persist/vault and later will create objects under /persist/vault/volumes/
Do we need to verify that wehave received and completely processed the EdgeNodeCluster.ClusterType before we start using /persist/vault/volumes?
There was a problem hiding this comment.
At first boot when the node is running as single node it will enforce PVC creation using the longhorn storage class which uses /persist/vault/volumes/replicas. The user ability to deploy volumes in local-path is not available until after convert to k3s_basemode with the cluster config.
Description
CLUSTER_TYPE_K3S_BASE requires local-path storage installed by default so the default
k3s config will allow it in base config.yaml. CLUSTER_TYPE_REPLICATED_STORAGE will copy
in an override k3s config file which disables it.
Local-path storage is configured in the k3s config.yaml base config file to place all volumes in /persist/vault/volumes by default.
PR dependencies
None
How to test and validate this PR
Changelog notes
Enable local-path storage for HV=k
PR Backports
Checklist
And the last but not least:
check them.
Please, check the boxes above after submitting the PR in interactive mode.