When you get a failure from your CI/CD pipeline regarding permission denied reasons, you should change them accordingly so that all users could access the oc tool.
The resolution is to provide 751 permissions or any other needed, but make some that user that executes the pipeline will be able to run the oc tool. Personally I added execute for others and I could bypass the error.
In order to create a CI/CD pipeline with gitlab built-in functionality you should firstly create the appropriate .gitlab-ci.yml file. This is the file on which the steps will be described for the pipeline.
This file should be placed on the root structure of the branch and every time a commit is pushed on the remote repository the steps will run. Instructions have been provided from gitlab and can be found here
For this example I chose gitlab runner as the building tool and the deployment method of a docker container.
In order to install gitlab runner as a container perform the below steps:
Register gitlab with your runner. You should get the registration token and runner url from your repository settings.
Inspect container and press gitlab-runner register
Start the runner
The runner should have been registered on your gitlab environment
Perform a commit and push changes to your repository
The run task should have started
Check the pipeline and see its status
The job was not succesful and by checking the logs I could verify that DNS resolution could not be enstablished.
In order to fix that you should add an entry for your named gitlab container to your gitlab runner. Unfortunately there are no tools like vim, nano installed on gitlab-runner. However you can bypass this by echoing a value in your /etc/hosts file.
It is also important that your local computer can resolve by fqdn your gitlab deployment. This is necessary because docker should be able to read this entry and perform actions on it.
After those changes you will be able to run your pipeline successfully.
Portainer is a fantastic tool that includes a GUI in order to manage your container workloads easier than with command line. It is free to use with a community edition and the documentation describes the installation which will take one approximately 5 minutes to complete.
In this article I will show you how to use portainer and its GUI to deploy a gitlab container on your setup.
If you use the default setup instructions then your instance will be created on localhost under 9000 port.
Lets assume you have configured ansible on multiple Windows hosts in order to massively perform patches installation or execute commands. As explained in detail on my previous articles in order to be successful the connection method must be set as winrm (see below)
However if you state this connection method, you cannot connect to linux machines and delegate tasks. One example of this scenario is a windows patching mechanism with wsus and ansible. You can deploy the patches using winrm method but you cannot log output on your localhost as the connection must be changed to ssh.
In order to bypass this problem I added a new group on my inventory for localhost entry for which I specify the connection method and user