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

k3s - update on the air-gap installation instruction #123

Open
1 of 3 tasks
btat opened this issue Apr 28, 2023 · 1 comment
Open
1 of 3 tasks

k3s - update on the air-gap installation instruction #123

btat opened this issue Apr 28, 2023 · 1 comment

Comments

@btat
Copy link
Contributor

btat commented Apr 28, 2023

Original issue: https://github.com/rancher/docs/issues/2351

Copying over relevant bits from original issue since K3s docs have been moved off the old rancher/docs repo.


During the validation for this issue: rancher/rancher#25495 (comment)

I found there are some improvements we can do for the documentation for k3s air-gap installation: https://rancher.com/docs/k3s/latest/en/installation/airgap/

  • for the section Prepare Images Directory, add some explanation for why we still need this when we have a private registry
  • for the section Create Registry YAML, add some explanation for when and how the private registry will be used by k3s, why the private registry is not used for k3s' own images
  • for the section Install K3s, add a sample command when installing k3s with an external database
@rancher-max
Copy link
Contributor

rancher-max commented Jul 12, 2023

Adding to this, we may also want to document that it is okay and sometimes advisable to remove the *.tar* files after initial startup when doing the tarball airgap method. This is because, when those files are present, restarts of the systemd service can take a long time to unpack those files since startup doesn't know that what is inside those files hasn't changed since the last start.

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

No branches or pull requests

2 participants