-
Notifications
You must be signed in to change notification settings - Fork 70
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
Updated airgap.md with steps to setup rancher and harvester in air-gapped env #371
base: main
Are you sure you want to change the base?
Updated airgap.md with steps to setup rancher and harvester in air-gapped env #371
Conversation
Referencing #137 (comment), should 4. Install Rancher be added to the beginning of the section "Deploy Rancher on K3s and setup private registry in another VM" or should this link replace these steps? |
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.
@@ -13,6 +13,369 @@ This section describes how to use Harvester in an air gapped environment. Some u | |||
|
|||
The Harvester ISO image contains all the packages to make it work in an air gapped environment. | |||
|
|||
## Working without HTTP Proxy |
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.
## Working without HTTP Proxy | |
## Working without HTTP proxy |
1. Edit [settings.yml](https://github.com/harvester/ipxe-examples/blob/c8267b6270660255bf71149a1fef3a7a914550de/vagrant-pxe-harvester/settings.yml#L44) and set `offline: true`. | ||
1. Execute the [setup_harvester.sh](https://github.com/harvester/ipxe-examples/blob/main/vagrant-pxe-harvester/setup_harvester.sh) script. | ||
|
||
### Deploy Rancher on K3s and setup private registry in another VM |
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.
### Deploy Rancher on K3s and setup private registry in another VM | |
### Deploy Rancher on K3s and set up a private registry in another VM |
chmod +x ./rancher-load-images.sh | ||
``` | ||
|
||
1. Make `get-rancher` script be excutable. |
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.
1. Make `get-rancher` script be excutable. | |
1. Make the `get-rancher` script excutable. |
./rancher-save-images.sh --image-list ./rancher-images.txt | ||
``` | ||
|
||
1. Load images to local registry. |
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.
1. Load images to local registry. | |
1. Load images to the local registry. |
curl -L -o cert-manager/cert-manager-crd.yaml https://github.com/jetstack/cert-manager/releases/download/v1.7.1/cert-manager.crds.yaml | ||
``` | ||
|
||
1. Remove the `vagrant-libvirt` network interface. Once the required resources download, you can remove the network. |
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.
1. Remove the `vagrant-libvirt` network interface. Once the required resources download, you can remove the network. | |
1. Once the required resources are downloaded, you can remove the `vagrant-libvirt` network interface. |
1. Edit [settings.yml](https://github.com/harvester/ipxe-examples/blob/c8267b6270660255bf71149a1fef3a7a914550de/vagrant-pxe-harvester/settings.yml#L44) and set `offline: true`. | ||
1. Execute the [setup_harvester.sh](https://github.com/harvester/ipxe-examples/blob/main/vagrant-pxe-harvester/setup_harvester.sh) script. | ||
|
||
### Deploy Rancher on K3s and setup private registry in another VM |
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.
### Deploy Rancher on K3s and setup private registry in another VM | |
### Deploy Rancher on K3s and set up a private registry in another VM |
chmod +x ./rancher-load-images.sh | ||
``` | ||
|
||
1. Make `get-rancher` script be excutable. |
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.
1. Make `get-rancher` script be excutable. | |
1. Make the `get-rancher` script excutable. |
./rancher-save-images.sh --image-list ./rancher-images.txt | ||
``` | ||
|
||
1. Load images to local registry. |
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.
1. Load images to local registry. | |
1. Load images to the local registry. |
curl -L -o cert-manager/cert-manager-crd.yaml https://github.com/jetstack/cert-manager/releases/download/v1.7.1/cert-manager.crds.yaml | ||
``` | ||
|
||
1. Remove the `vagrant-libvirt` network interface. Once the required resources download, you can remove the network. |
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.
1. Remove the `vagrant-libvirt` network interface. Once the required resources download, you can remove the network. | |
1. Once the required resources are downloaded, you can remove the `vagrant-libvirt` network interface. |
192.168.0.50 myregistry.local myrancher.local | ||
``` | ||
|
||
### Integrate Harvester with Rancher in air-gapped environment |
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.
### Integrate Harvester with Rancher in air-gapped environment | |
### Integrate Harvester with Rancher in an air-gapped environment |
✅ Deploy Preview for harvester-preview ready!
|
Added steps for per original PR #137: