dudash / openshift-workshops Goto Github PK

Not sure if you guys are interested in adding a redis DB to the guestbook. I did not want to hack up the workshop source and create a PR if you feel it's overkill.

$ oc new-app docker.io/kubeguide/redis-master

Wait for the redis pod to become ready then redeploy the guestbook.

$ oc deploy guestbook --latest

https://docs.mapbox.com/help/troubleshooting/migrate-legacy-static-images-api/#migrating-studio-classic-style-template

Do a site-wide search for Open Shift, Openshift, etc...Ive seen the spelling of the word "OpenShift" vary, but it should be consistent.

create a new section for 3.4, and update directions and screenshots

Possible Ideas:

1. A lab that walks the user through authenticating against a private repo
2. A lab that allows a user to create a secret and then display the secret on a page
3. A lab that allows the user to create a secret and then authenticate into a part of the workshop application

Screenshots are all over the place and in many cases the same screenshot is copied into 2 or more folders. Lets create a "shared" folder for screenshots/images at the top level of the page hierarchy, and then folders for very specific labs.

Update to work with latest 4.x SCL version of Node.js. Also, shrinkwrap and tag as a new release.

Reported by J.Osborne and I've seen the same behavior. When you update the variable redeploy to OCP, the code changes but the UI never updates. Creating a bug here so I do not forget to investigate and apply a fix.

Updates to 3.3 and 3.4 make adding a storage lab feasible. The lab can show:

• creating a PVC and see it claim a PV
• Mount PVC to pods via DC
• Write data to PVC
• Kill pods
• Bring pod back up
• Verify that state has been retained

Find references in offline labs that point to http://openshift.example.com:3000 and update to have the correct URL. Maybe the answer is to let the proctor define the URL for the offline repos during the lab and then the participants would use that information to plug in the correct git URL. Either way, a hardcoded URL is not intuitive if the directions state to use that URL and it does not exist.

example can be found in: http://dudash.github.io/openshift-workshops/www/3.3/offline/workshop-lab3-s2inodejs.html

the CI/CD pipeline lab leaves out a lot of steps and makes assumptions that don't line up with the screenshots. Update the directions so that it includes creating the proper project/apps/

If you use the drop down to select 3.3 labs and then use the back button to go back to the main landing page, the "3.3" selection will remain, but the links will still be the ones for the 3.1/3.2 labs.

Expected: If you navigate back, the links should represent what the selector indicates.

Browser: Chrome 54.0.2840.98