This message was deleted.
# general
a
This message was deleted.
a
I'm in the same boat as you
a lot of dependencies (installs) from external sources
while I was able to get initial install completed airgapped, it was not an easy task (more because of the private registry and all of the rancher images)
have to not use the tools to create clusters via rancher because of that reason
unless I can figure out how to make a local repo for "Default Docker engine installation URL"
b
I have no idea how to setup local repo for apps
thinking just create a proxy for it
If you will be able to find solution for apps private registry let me know
a
I might go down the proxy route as well
no easy way to get all of these external dependencies
Rancher docs say "Alternatively, it is also possible to set up Rancher completely air-gapped without any Internet access. This process is described in detail in the Rancher docs."
while you can install it initially air gapped
I don't see how you can continue air gapped and use the tools for creating clusters and growing them adhoc
would have to create the clusters outside of rancher and then import
and add nodes not using rancher to existing clusters
Talk about frustrating. Anyone else configure rancher infra to use proxies ? I don’t see rancher even attempting to use the proxy in the proxy logs 😕 there is the proxy /no proxy setting you do add to the start of rancher then you can also add variables (http_proxy /no proxy) to new clusters being created. I must be missing something or doing something wrong.
s
You can. In the cluster creation you can use a local registry as a mirror.
a
That’s a docker registry though
But it also tries to use other resources that are not docker registries
s
For cluster creation?
a
For instance it would try to install kubernetes
Yeah
Why I was trying to make it use a proxy but having difficulties configuring that
s
Never been my experience. The images are all from rancher docker registry namespace. Can you explain further which images you are trying to get?
How are you creating the proxy?
a
Kiberneties install is not an image
It’s just a normal web proxy
Just like any other web proxy
s
Ok. Use a local container registry like sonatype nexus or artifactory
a
Kuberneties install is not an image though
You need something to put the images into
It can’t install kubernetes in cluster creation
I’m using Ubuntu cloud image so it’s doesn’t come with anything
s
Yes it is. All our clusters have no internet access and we mirror through nexus. Works like a charm
a
It’s supposed to install rke1 (or rke2) depending what I pick
s
I have tracked what images it uses.
a
So are you telling it to use a local private registry
s
As a mirror. Yes
a
Or are you also telling it to use a proxy as well
I made a simple docker private registry with images from rancher
s
Mirror a local private registry
a
On rancher 2.7
s
You can tell it to use a private registry too
There are multiple options
a
I must be missing something then
Even if I wasn’t using a private registry
The proxy should be handling the outbound
But it doesn’t even seem that it’s even trying to use the proxy
To go outbound
s
for getting what?
Have you looked at this?
a
yeah, private registry...
example
when creating a rke1 cluster via ranger
the nodes fail to get any further when they attempt that step
s
Why are you using rke1?
a
hehe
that's beside the point
same thing happens when creating rke2
just not that step
they try to install external resources to install software and it can't
rke2 would need to install rke2 before it can put any images into it
s
Rke has an airgapped way of installing it
Yoy don't need to access internet
Rke2
a
I can install it manually airgapped
I can't install it when using rancher to deploy
my issue currently
s
So when you use rancher to deploy use with a local container registry 😊
a
the airgap docs only speak of manual initial installs
and you are using your own OS images?
or the rancherOS ones?
(curious)
s
Own images
a
will try other registry offerings
maybe like you said they have more options (mirror helm repos, etc)
s
My work flow is use packer to build base linux os image that has dependencies for long horn and such
Then i use that resultant 'template' to deploy using rancher