Skip to content

fix: copy /system/providers/ from stylus image to support stylus v4.10.x on kubeadm nodes #737

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

Open
birendrasingh7698 wants to merge 1 commit into
base: vipsharm-GPU
Choose a base branch
from
Open

fix: copy /system/providers/ from stylus image to support stylus v4.10.x on kubeadm nodes #737

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 5 additions & 0 deletions Earthfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -643,6 +643,11 @@ provider-image:
COPY +stylus-image/oem/stylus_config.yaml /etc/kairos/branding/stylus_config.yaml
COPY +stylus-image/etc/elemental/config.yaml /etc/elemental/config.yaml
COPY --if-exists "$EDGE_CUSTOM_CONFIG" /oem/.edge_custom_config.yaml
# stylus v4.10.x ships agent-provider-kubeadm alongside agent-provider-stylus in
# /system/providers/. Without this copy the runtime upgrade rsync tries to write
# agent-provider-kubeadm to /system/providers/ which is read-only at runtime,
# causing cluster creation to hang at "Upgrading provider image" on kubeadm nodes.
COPY --if-exists +stylus-image/system/providers/ /system/providers/

IF [ "$IS_UKI" = "true" ]
COPY +internal-slink/slink /usr/bin/slink
Expand Down