rh-mobb/aro-workshop-content

Repository for hackathon content that will be publicly available.

aro-workshop-content's Issues

Provide a single voice of the workshop

After all the content is in place, go through and update the content to reflect a single voice.

60% done

Validate Making the Workshop Application Resilient

Using the v2 branch, validate and update the 'Make the workshop application resilient' section.

90% complete

Define the developers track

Assuming we have an administrator and developer track, working from the v2 branch, split up the workshop into content just for developers.

Create a ROSA version

Taking the output of the ARO workshop, rewrite relevant parts to use the use ROSA and AWS services.

0% done

Cluster Autoscaler tutorial cleanup

I've walked through the end of the Cluster Autoscaler tutorial. Would we want to scale down the machineset back to 1 when we're done with this section? If not, the following sections will run with 3 machines in an AZ rather than 1, and won't match the output that is being reported.

Update / Validate Preparing the Cluster

Using the v2 branch, validate and update the 'prepare the cluster and environment section'.

Update the content to remove the Azure Service Operator part.

Remove ARC integration. Work with the 'Observability' issue if needed to add observability tools.

60% complete

Define Personas and Tracks

The current structure of the workshop ( see the v2 branch ) has a single track for Administrators, Developer, and Operations.

What persona's should we target and how many should there be?

From a logistics perspective, if there is more than one, will all personas be in the same room? If so, how will we handle guiding attendees through the workshop.

Validate Getting Started Section

New to v2 of the workshop is having attendees create a new cluster at the beginning of the workshop.

Refine and validate the getting started section where attendees create a new cluster and retrieve credentials.

90% complete

Add observability content

The current workshop lacks detailed content on observability.

Define and Develop content for observability using Azure services for an administrator or operations person.

Net new

Refine Service Mesh Content

Following the same structure of the v2 branch, where a single application is used throughout the workshop, rewrite the service mesh part to use the same application.

For weighted load balancing / Istio Gateway, use the output of the 'automate deploying and application' that creates a v2 version of the frontend micro-service along with the original version.

25% complete

Validate Deploying the Workshop Application

Using the v2 branch, validate and update the 'deploy the workshop application' section.

90% complete

Validate Managing Nodes

Using the v2 branch, validate and update the 'managing nodes' section.

90% complete

Refine and Validate Automate Deploying an Application

Using the v2 branch, validate and update the 'Automate Deploying an Application' section.

The output should be a v2 version of the application that the service mesh section will use for weighted load balancing.

75% complete

Define the Administrator track

Assuming we have an administrator and developer track, working from the v2 branch, split up the workshop into content just for administrators.

Validate Exposing the workshop application

Using the v2 branch, validate and update the 'Exposing the workshop application' section.

90% complete

Validate ARO Day X Operations

Using the v2 branch, validate and update Managing Upgrades as part of the 'ARO Day X Operations' section.

Add addition content to operations tasks if desired. Coordinate with the observability issue.

40% complete