We have our fleet of servers getting packages through local RPM mirrors, and we have the kubernetes mirror hosted as a local mirror. However, every time I run the installer it puts back the kubernetes.repo file, which causes DNF errors due to us not allowing this traffic to this destination. We have limited outbound access to the web on these servers, which is why we sync everything in a local repository.
Is there any logic you can put in to see if an equivalent mirror to the kubernetes upstream mirror is already on the system before dropping this .repo in place? And/or maybe a setting to stop it from being put in place?
Thanks in advance!
We have our fleet of servers getting packages through local RPM mirrors, and we have the kubernetes mirror hosted as a local mirror. However, every time I run the installer it puts back the kubernetes.repo file, which causes DNF errors due to us not allowing this traffic to this destination. We have limited outbound access to the web on these servers, which is why we sync everything in a local repository.
Is there any logic you can put in to see if an equivalent mirror to the kubernetes upstream mirror is already on the system before dropping this .repo in place? And/or maybe a setting to stop it from being put in place?
Thanks in advance!