Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

Kubecf deployment in air gapped environment #1685

Open
gsachdev6 opened this issue Jan 13, 2021 · 3 comments
Open

Kubecf deployment in air gapped environment #1685

gsachdev6 opened this issue Jan 13, 2021 · 3 comments
Assignees
Labels
Type: Enhancement New feature or request

Comments

@gsachdev6
Copy link

Is your feature request related to a problem? Please describe.
I want to deploy kubecf in an air gapped environment where I do not have access to internet to download the images and binary.

Describe the solution you'd like
Can you please provide me either:

  1. List of all the docker images, OS images, builder images, etc. that I can manually download and upload them in my local repository.
  2. List of all the yaml files where i need to make the changes to get my local repo configured.

Describe alternatives you've considered
I tried doing that manually but I got stuck to understand which all images need to be changed.

Additional context
Add any other context or screenshots about the feature request here.

@gsachdev6 gsachdev6 added the Type: Enhancement New feature or request label Jan 13, 2021
@jandubois
Copy link
Member

There are imagelist.txt files in the cf-operator and kubecf helm charts that list all required images.

The SUSE CAP product puts all images into a single registry, and the imagelist.txt files have been stripped of the source registry and only contain the image names and tags. There is a sample script to mirror the images in the documentation at https://documentation.suse.com/suse-cap/2.1/single-html/cap-guides/#sec-cap-air-gap-registry

I'm not sure if the documentation is still accurate, but it should give you a starting point...

@gsachdev6
Copy link
Author

Thanks a lot for your response and I am able to create the script. But when I run the script, I am not able to download anything from suse registry, is it a private repo that I require access on ?

Everytime either I run "docker login" or "docker pull", it gives me error

error response from daemon: get https://registry.suse.com/v2/: unauthorized: authentication required

Any guidance will be greatly appreciated here as I am stuck getting this deployed.

@jandubois
Copy link
Member

@gsachdev6 It is not a private registry; or at least you can pull images without being logged in:

Random example I just tried, and it worked for me:

docker pull registry.suse.com/cap/suse-nginx-buildpack:SLE_15_SP1-27.7-7.0.0_374.gb8e8e6af-1.1.15.1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants