dlbewley

# if you don't want to just use --authfile or set REGISTRY_AUTH_FILE for whatever reason
# you may login to each registry in your pull secret thusly
# spoiler alert, here's how to extract usernames and passwords from your pull secret

PULL_SECRET_PATH=pull-secret.json

for R in $(jq -r '.auths|keys[]' $PULL_SECRET_PATH ); do
  echo "Logging into $R"
  U=$(jq -r ".auths.\"$R\".auth" $PULL_SECRET_PATH | base64 -d | awk -F: '{print $1}')
  P=$(jq -r ".auths.\"$R\".auth" $PULL_SECRET_PATH | base64 -d | awk -F: '{print $2}')

tosin2013

#!/bin/bash
set -xe 
CHECKLOGGINGUSER=$(whoami)
if [ ${CHECKLOGGINGUSER} == "root" ];
then 
  echo "login as sudo user to run script."
  echo "You are currently logged in as root"
  exit 1
fi

acsulli

On-prem Single Node OpenShift without Assisted Installer

Special thanks to Ben Schmaus and his amazing blog post.

We also discussed the process here during the Ask an OpenShift Admin live stream on Oct 20th.

1. Pre-reqs

   Download the tools we'll need.

acsulli

Configuring Active Directory authentication with OpenShift 4

1. Understand AD LDAP structure and naming. Read the docs on the components

   Refer to the OpenShift docs for the LDAP identity provider and LDAP group syncing.

2. Create the OAuth config

   # create a secret for the bindDN user password

tosin2013

#!/bin/bash 
set -xe
if [ -z $1 ];
then 
  echo "Please pass user to be created."
  echo "USAGE: $@ username"
  exit 1
fi

USER=${1}

cdoan1

#!/bin/bash
#
# Reference: https://www.openshift.com/blog/openshift-4-2-disconnected-install
#
HOSTNAME=`hostname`
USERNAME=admin
PASSWORD=password

yum -y install podman httpd httpd-tools
mkdir -p $(pwd)/registry/{auth,certs,data}

tosin2013

Deploying a Simple Utility Service in OpenShift

This document outlines the steps for deploying a basic utility service in OpenShift using the oc command-line tool and Docker images.

What it does

This script creates a deployment for a service named utilities with the following functionalities:

• Runs the fedora:latest Docker image.
• Installs essential utilities like nc, wget, curl, bind-utils, iputils, net-tools, and telnet.

dmesser

What is this about?

This gist describes how to set up standalone kubelet + CRI-O + CNI on Fedora Core 31. The goal is to place a Kubernetes Pod manifest on an single node and access the application from the network. This guide has been tested on x86-64 and armv7 deployments.

Prepare the system

Make sure the system is up to date:

dnf -y update

williamcaban

OCP 4.2/4.3 All-In-One (UPI mode)

This document assume reader is familiar with the OCP4x installation process.

Before Deployment

• Setup the install-config.yaml to deploy a single master and no workers

  apiVersion: v1
  baseDomain: example.com
  

flyemsafe

Configure USB device

• Ensure all required packages are installed

dnf install grub2-efi shim gdisk grub2-efi-modules grub2-efi-x64-modules

• Define USB device varaible