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

Support air-gapped installation #400

Open
sancho21 opened this issue Mar 19, 2024 · 0 comments
Open

Support air-gapped installation #400

sancho21 opened this issue Mar 19, 2024 · 0 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@sancho21
Copy link

I'm trying to install it in an air-gapped environment (no internet access available). In order to do the installation I prefer Helm chart, but I have to pass variable this way:

helm install -n openelb-system --create-namespace openelb openelb-*.tgz --set admission.image.repository=repository:5000/kubespheredev/kube-webhook-certgen --set manager.image.repository=repository:5000/kubesphere/openelb

I'd be good if there's a possibility to do like most people do --set global.imageRegistry=myprivate-docker-registry.local:5000 variable

Another thing is, somehow I found that the chart doesn't explicitly show the need of aledbf/kube-keepalived-vip:0.35 (it's not visible in helm template command). So, I have to download the image after kubectl shows that OpenELB needs it. Moreover, there's no way to override the image registry location. No option to do something like --set keepalived.image.repository=repository:5000/aledbf/kube-keepalived-vip:0.35

In the end, I still failed to make use of OpenELB in my air-gapped environment

@sancho21 sancho21 added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 19, 2024
@renyunkang renyunkang self-assigned this Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants