Nate Revo therevoman

In some baremetal and private Cloud deployments we need to force masters nodes to sync clocks. This is required by etcd and for the validity of the installation certs.

Force time sync

sudo chronyc -a makestep

To force clock update (without stepped updates) /etc/chrony.conf

OpenShift Client, RHCOS and Installer

Public Mirror for OC Client, RHCOS and Installer: https://mirror.openshift.com/pub/openshift-v4/
- Latest stable OCP client https://mirror.openshift.com/pub/openshift-v4/clients/ocp/latest/
- To identify the hash for the latest stable refer to the Pull From line in the release.txt

OpenShift CI

OpenShift/OCP Release Status https://openshift-release.svc.ci.openshift.org
OKD Release Status https://origin-release.svc.ci.openshift.org

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
```

OpenShift Named Certificates

This is a short guide explaining how to deploy and manage custom SNI or "named" certificates via openshift-ansible. These custom certificates will be served for public facing console and API.

1. Setting up
2. Install using master.public-example.com certificate

Configure 1G Hugepages in OpenShift 4.2

Update Node Kernel Parameters

Supporting 1G hugepages requires the Kernel to support 1G Hugepages. This is done by applying a boot Kernel parameter.

Create a MachineConfig (MC) to apply to the Node type that will be using the 1G hugepages. The following example set 1G hugepages for all worker nodes 50-kargs-1g-hugepages.yaml:
```
apiVersion: machineconfiguration.openshift.io/v1
```

kind: MachineConfig

This gist is mostly based on the dnsmasq appendix from the openshift-training repo. However, I updated it and included fixes for the many gotchas I found along the way.

This is useful for folks who want to set up a DNS service as part of the cluster itself, either because they cannot easily change their DNS setup outside of the cluster, or just because they want to keep the cluster setup self-contained.

Add the following chunk to your existing ISC dhcpd.conf file.

if exists user-class and ( option user-class = "iPXE" ) {
    filename "http://boot.smidsrod.lan/boot.ipxe";
}
else {
    filename "undionly.kpxe";
}

(or see https://gist.github.com/4008017 for a more elaborate setup

	#!/bin/sh

	IMAGES=`oc get is -o go-template --template="{{range .items}}{{.metadata.name}} {{end}}" -n openshift`

	for i in ${IMAGES}; do
	echo "Pulling: $i"
	./oc import-image $i --all -n openshift
	done

	# User privileges
	# Add admin privileges to user in particular project
	$ oc adm policy add-role-to-user admin <user> -n <project>

	# Add cluster-admin privileges to user
	$ oc adm policy add-cluster-role-to-user cluster-admin <user>


	#Reference
	https://docs.openshift.com/container-platform/latest/admin_guide/manage_rbac.html#managing-role-bindings

	[profile]
	layer_height = 0.16
	wall_thickness = 1.2
	retraction_enable = True
	solid_layer_thickness = 1.2
	fill_density = 10
	nozzle_size = 0.4
	print_speed = 50
	print_temperature = 200
	print_temperature2 = 0