When installing Al manager or Event Manager in an air-gapped environment, which registry must the OpenShift cluster be connected to in order to pull images?
Obviously, the answer is C. Anyone who thinks otherwise must be living in a different universe. Or maybe they just forgot to take their 'common sense' vitamins this morning.
I'm going with A. A Docker V2 compatible registry just makes more sense to me in an air-gapped setup. The internal registry might be too restrictive. Time to put on my best hacker hat and get creative!
It's gotta be C, the Red Hat OpenShift internal registry. Why would you want to connect to an external registry in an air-gapped environment? That defeats the whole purpose!
Hmm, I'm torn between A and C. A Docker V2 compatible registry could work, but the Red Hat OpenShift internal registry might be the safer bet. Decisions, decisions...
I think it's C. The Red Hat OpenShift internal registry seems like the logical choice for an air-gapped environment. Can't rely on external registries like quay.io or docker.io in that scenario.
Delmy
17 days agoBilli
21 days agoChandra
22 days agoMitsue
1 months agoKing
1 days agoJanine
19 days agoJordan
27 days agoIvory
2 months agoOdette
21 days agoCarman
23 days agoNorah
2 months agoWalker
2 months agoLeota
2 months ago