action #107764
closedcoordination #107755: [epic] BCI testing on OpenShift
[Investigation] Install OC binary to manage OpenShift environment
0%
Description
oc is the CLI tool that allows managing an OpenShift clusters.
However, it's not publicly available and it can only be downloaded from https://access.redhat.com/downloads/content/290, which requires an account registered (no payment needed).
This will download a tarball oc-4.9.22-linux.tar.gz, that after extracting it contains 2 binaries and a README.
$ ls -lh oc-4.9.22-linux
total 479992
-rw-r--r--@ 1 jlausuch staff 954B Feb 14 10:58 README.md
-rwxr-xr-x@ 2 jlausuch staff 117M Feb 14 10:58 kubectl
-rwxr-xr-x@ 2 jlausuch staff 117M Feb 14 10:58 oc
The tool of our interest here is just oc, we can get kubectl by other ways.
The idea is to investigate how we could to get this binary from other trusted sources without a registered RH account (if possible) and install it at runtime during the tests or in our Public Cloud helper VM.
Another possibility is to create a project in IBS and push that binary and keep it up to date with new updates, but that might require manual intervention, and still, a RH account to download the binary.
Files
Updated by jlausuch over 2 years ago
- Tracker changed from coordination to action
Updated by ilausuch about 2 years ago
- Status changed from Workable to In Progress
- Assignee set to ilausuch
Updated by ilausuch about 2 years ago
In order to no publish this package in a public accessible server:
Two initial options:
- Use identified S3
- IBS
Using S3.
pros: We have already a AWS account with some buckets. We can create one with identification and read-only access
cons: We need to have the AWS tools installed in order to download the image from S3 using authentification or we can use shared pressigned URLS https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html this url has a period of time of aliveness but can be set by user
Updated by jlausuch about 2 years ago
ilausuch wrote:
In order to no publish this package in a public accessible server:
Two initial options:
- Use identified S3
- IBS
Using S3.
pros: We have already a AWS account with some buckets. We can create one with identification and read-only access
cons: We need to have the AWS tools installed in order to download the image from S3 using authentification or we can use shared pressigned URLS https://docs.aws.amazon.com/AmazonS3/latest/userguide/ShareObjectPreSignedURL.html this url has a period of time of aliveness but can be set by user
How difficult would be to package it in IBS so we can just do zypper ar <some_repo> and zypper in osc ?
Updated by ilausuch about 2 years ago
A PR to install oc from a url https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14942
Updated by ilausuch about 2 years ago
- Status changed from In Progress to Resolved