We recently released a new version of the runner operator that enables users to install the runner in air-gapped environments.
Problem
For now, we don't have a way to install GitLab Runner Operator on a Kubernetes/Openshift cluster on an isolated network.
For example, we have a customer that has a Kubernetes instance on an isolated network. They follow the steps listed here to install the GitLab Runner operator on their Kubernetes cluster.
They were able to override the image for cert manager and OLM, but when it came to installing the Operator via the command kubectl create -f https://operatorhub.io/install/gitlab-runner-operator.yaml, the job that OLM generated to install the operator failed as it won't be able to pull the image required for the job.
On my test, installing the GitLab Runner Operator will trigger a job in the olm namespace that requires the following images:
There is no clear way on how to override these images. In the customer's case, the job is failing as they only have a trusted registry to pull the image from.
The scope of this issue is to add a section to the install GitLab runner operator docs that covers the configuration steps required to install the Runner Operator on a Kubernetes cluster in an air-gapped environment.
@ggeorgiev_gitlab it would be good to get your take on this one. Do you think the workaround you described for OpenShift can be applied for the generic Operator? However, at closer look, it seems that from the error in the issue description, that workaround does not seem viable.
If you do not feel the purpose of this issue matches one of the types, you may apply the typeignore label to exclude it from type tracking metrics and future prompts.
As described here, I don't think there's anything we can do other than documentation on how to change the manager image, if that is not true feel free to suggest alternatives
As to OLM, we don't have control over it, so I don't think we can do much about it.
@DarrenEastman agreed, I think we can add this to the Operator install docs. @ggeorgiev_gitlab will you create the MR and I'll review? Or else if you can provide the steps to change the manager image I can go ahead and open the MR to document it.
I am looking for registering k8s runner on Openshift Platform in an air gapped env and I understand that using gitlab runner operators is not supported yet.
Can you let me know any other way we can register?
Especially #77 (comment 1041351388) - is this a workaround or is it not possible to do the offline install at all?
Customer query is
As per #77 (closed) (comment 1041351388), I am curious what the recommended method for installing the GitLab Runner Operator is in an air-gapped env. We need to be able to configure the registry to be something else like is possible in the Runner CR.
- Priority: ~customer priority:: 7- Why interested: Support offline/airgapped installation of GitLab Runner Operator- Problem they are trying to solve: We need to be able to install the GitLab Runner Operator in an airgapped environment. We use the docs here: https://operatorhub.io/operator/gitlab-runner-operator- Current solution for this problem:Remove GitLab Runner Operator from our installation to unblock our deployment. There is no other workaround we have as of yet.- Impact to the customer of not having this: Inability to use the GitLab Runner- Questions: Are there any workarounds that we can use in the meantime? If not, we will have to remove it for the time being.
Adding more context from the custoemr who has investigate into this
As per #77 (closed) (comment 1041351388), I am curious what the recommended method for installing the GitLab Runner Operator is in an air-gapped env. We need to be able to configure the registry to be something else like is possible in the Runner CR.
'd like to add that the recommended solution there won't entirely fix the problem to my knowledge as there are still hard-coded images within the code for the GitLab Runner Operator that need to be updated as well (as far as I understand it).
I am curious if we would be able to build our own catalog for this operator but with custom images in the meantime, but I would require some help understanding the steps we need to take to achieve that.
I'd also like to learn if there are any kinds of workarounds available for the time being. It looks like there will need to be several code changes made for this to work, and we'd like to know if we could take some action to make this work for us sooner.
This issue is labelled as as docs-only, @DarrenEastman please consider removing this.
I'll suggest that the customer can consider making a merge request to advance this issue than the current scheduling.
Darren Eastmanchanged title from Support offline install of the GitLab Runner Operator to Add documentation on how to configure an offline install of the GitLab Runner Operator
changed title from Support offline install of the GitLab Runner Operator to Add documentation on how to configure an offline install of the GitLab Runner Operator
Darren Eastmanchanged title from Add documentation on how to configure an offline install of the GitLab Runner Operator to Add documentation on how to configure an air-gapped (offline) install of the GitLab Runner Operator
changed title from Add documentation on how to configure an offline install of the GitLab Runner Operator to Add documentation on how to configure an air-gapped (offline) install of the GitLab Runner Operator