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.

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

kubevirt single node install path rework and upgrades. #3838

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andrewd-zededa
Copy link
Contributor

@andrewd-zededa andrewd-zededa commented Mar 29, 2024

Longhorn:
Bump to latest version 1.6.0 including upstream change to
find the correct iscsid pid when running k3s in a container.
nsmounter replacement to fix PID enabling RWX PVC mounts
findutils: needed for -regextype option
nfs-utils: for RWX (nfs) PVCs
longhorn-generate-support-bundle.sh:
request a support bundle containing complete lh logs
written to longhornsupportbundle_*.zip in
/persist/newlog/kube/
Lowered iSCSI queue depth to handle large CDI volume uploads.
This is temporary until performance testing completes.
Set default disk path (pool) to /persist/vault/volumes

K3s:
Bump to version v1.28.5+k3s1
k3s-pod-logs.sh: collect kube /var/log/pods/ contents
for complete k3s pod logs. CDI, kubevirt, kubesystem, ...
On k3s restarts compress /persist/newlog/kube/k3s.log to
k3s.log.restart..gz for root cause analysis.
Otherwise regular k3s log rotation can lose the crashes after
the system becomes stable for some time.
Config:
Switched from etcd to SQLite for perf on
smaller nodes.

Containerd:
containerd-user root moved to /persist/vault/containerd

CDI:
Bump to version 1.57 to include qcow import readahead fix

Kubevirt:
Bump to version 1.1.1
Yetus fixes in kubevirt-features.yaml

Including debuguser role by @naiming-zededa .

Copy link

codecov bot commented Mar 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 17.51%. Comparing base (7859da6) to head (4c5e659).
Report is 9 commits behind head on master.

❗ Current head 4c5e659 differs from pull request most recent head c1c22e4. Consider uploading reports for the commit c1c22e4 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3838   +/-   ##
=======================================
  Coverage   17.51%   17.51%           
=======================================
  Files           3        3           
  Lines         805      805           
=======================================
  Hits          141      141           
  Misses        629      629           
  Partials       35       35           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@andrewd-zededa andrewd-zededa force-pushed the andrewd-kubevirt-longhorn branch 3 times, most recently from dec0ef9 to 4c5e659 Compare April 1, 2024 19:35
@andrewd-zededa andrewd-zededa marked this pull request as ready for review April 1, 2024 20:40
Comment on lines +345 to +346
while true; do
if [ -e "$filename" ]; then
Copy link
Contributor

Choose a reason for hiding this comment

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

isn't it possible to check directly in the condition of the while loop that $filename exists instead of creating an endless loop and then inside check if the file exists and break if it does not?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

certainly yes

Copy link
Collaborator

@rene rene Apr 24, 2024

Choose a reason for hiding this comment

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

until [ -e "$filename" ]; do
...
done

is what are you looking for...


PROC_DIR="/proc"

os_distro_talos="talos"
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this from an existing file with talks support and you're adding eve support to it? If so can we upstream the eve support?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes the upstream work is going to be submitted soon

@eriknordmark eriknordmark requested a review from deitch April 7, 2024 13:29
Longhorn:
    Bump to latest version 1.6.0 including upstream change to
        find the correct iscsid pid when running k3s in a container.
    nsmounter replacement to fix PID enabling RWX PVC mounts
    findutils: needed for -regextype option
    nfs-utils: for RWX (nfs) PVCs
    longhorn-generate-support-bundle.sh:
        request a support bundle containing complete lh logs
        written to longhornsupportbundle_*.zip in
        /persist/newlog/kube/
    Lowered iSCSI queue depth to handle large CDI volume uploads.
        This is temporary until performance testing completes.
    Set default disk path (pool) to /persist/vault/volumes

K3s:
    Bump to version v1.28.5+k3s1
    k3s-pod-logs.sh: collect kube /var/log/pods/ contents
        for complete k3s pod logs.  CDI, kubevirt, kubesystem, ...
    On k3s restarts compress /persist/newlog/kube/k3s.log to
        k3s.log.restart.<restart count>.gz for root cause analysis.
        Otherwise regular k3s log rotation can lose the crashes after
        the system becomes stable for some time.
    Config:
        Switched from etcd to SQLite for perf on
            smaller nodes.

Containerd:
    containerd-user root moved to /persist/vault/containerd

CDI:
    Bump to version 1.57 to include qcow import readahead fix

Kubevirt:
    Bump to version 1.1.1
    Yetus fixes in kubevirt-features.yaml

Signed-off-by: Andrew Durbin <andrewd@zededa.com>
Copy link
Contributor

@eriknordmark eriknordmark left a comment

Choose a reason for hiding this comment

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

Andrew said he would split up this PR.

@andrewd-zededa
Copy link
Contributor Author

andrewd-zededa commented Apr 22, 2024

@eriknordmark @zedi-pramodh
The breakup of this PR is in progress:
part 1: #3877
part 2: #3878
part 3: #3881
part 4: #3883
part 5: #3893
part 6: #3895

@eriknordmark
Copy link
Contributor

@eriknordmark @zedi-pramodh The breakup of this PR is in progress: part 1: #3877 part 2: #3878 part 3: #3881 part 4: #3883 part 5: #3893 part 6: #3895

Are there more parts coming? I might want to wait to cut 12.1.0 until they are all in.

@andrewd-zededa
Copy link
Contributor Author

@eriknordmark sorry missed this, I believe all small broken up PRs of this are submitted. I think just waiting on merge of 3893 now.

@eriknordmark
Copy link
Contributor

@andrewd-zededa has all of these been split into separate PRs so we can close this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants