dudash

<map version="1.0.1">
<!-- To view this file, download free mind mapping software FreeMind from http://freemind.sourceforge.net -->
<node CREATED="1579015595111" ID="ID_510040451" MODIFIED="1580911541873" TEXT="endlesspods">
<node CREATED="1579016027245" ID="ID_828208452" MODIFIED="1579017057073" POSITION="left" TEXT="original design doc">
<node CREATED="1579016030182" ID="ID_1709960551" MODIFIED="1579016032070" TEXT="The game will start with the OpenShift Web Console UI when deleting a project and at the moment when the click goes to the confirm button it zooms in to the project&apos;s inside.   Inside the project, there is a pod that notices that everything is starting to fall apart so it starts to run. The objective of the game is to run the most you can. Is an endless runner so there is no end to the game. The more you run, the higher your ranking goes. "/>
</node>
<node CREATED="1579015614658" ID="ID_747976525" MODIFIED="1579017129332" POSITION="right" TEXT="gameplay">
<node CREATED="1579015621101" ID="I

dudash

apiVersion: v1
kind: Pod
metadata:
  name: awscli
spec:
  containers:
  - name: awscli
    image: amazon/aws-cli:latest
    # Just spin & wait forever
    command: [ "/bin/bash", "-c", "--" ]

dudash

Secure Demo Setup

This assumes you have a ROSA cluster and you have added an OIDC provider for the cluster. We will walk through the steps to auth ROSA pods to access specific S3 buckets. Instead of creating and distributing your AWS credentials to the containers or using the Amazon EC2 instance’s role, we will create a IAM Policy and Role (with federated identity) and associate it to some of the built-in ROSA service accounts.

Setup temp AWS creds

aws configure --profile rosa-demo

....answer questions....

export AWS_PROFILE=rosa-demo

dudash

apiVersion: keycloak.org/v1alpha1
kind: Keycloak
metadata:
  name: demo-oidc
  namespace: demo-oidc
spec:
  extensions: {}
  externalAccess:
    enabled: true
  externalDatabase:

dudash

Prerequisites OCP cluster 4.9+

Setup GPU Nodes

👉 Add a MachineSet for GPU Workers by exporting an existing worker's MachineSet and switching the instance type, name, and selflink. You have some choices here depending on what you want to do.

• Amazon EC2 P3 Instances have up to 8 NVIDIA Tesla V100 GPUs.
• Amazon EC2 G3 Instances have up to 4 NVIDIA Tesla M60 GPUs.
• Amazon EC2 G4 Instances have up to 4 NVIDIA T4 GPUs.
• Amazon EC2 P4 Instances have up to 8 NVIDIA Tesla A100 GPUs.

They're not cheap so check costs before picking, I demo with the g4dn.4xlarge (currently costs $1.204/hr)

dudash

Keybase proof

I hereby claim:

• I am dudash on github.
• I am dudash (https://keybase.io/dudash) on keybase.
• I have a public key ASAdVOl-PxBvCETOeqRGSlZi3nBJve6sulWkS6j0WDIc4Ao

To claim this, I am signing this object:

dudash

alias oc='noglob oc'

dudash

apiVersion: v1
kind: Namespace
metadata:
  name: openshift-serverless

---
apiVersion: v1
kind: Namespace
metadata:
  name: openshift-workspaces

dudash

#!/bin/bash
# source: https://gist.github.com/dudash/f7cef9a30a76f59ca7f9ebfa3d803b0e/
# docs: https://docs.openshift.com/container-platform/4.7/cli_reference/openshift_cli/extending-cli-plugins.html
#
# To use this:
#   put this script in /usr/local/bin
#   chmod a+x oc-version+
#   oc version+
oc version
echo "Cluster ID:" $(oc get clusterversion -o jsonpath='{.items[].spec.clusterID}')

dudash

alias brew='arch -x86_64 brew'