update guestbook example for 2.0

[cdoan1]

Description of the change:

• demo content should reflect api changes in the 2.0 release

Motivation for the change:

• guestbook demo subscription can't be applied without the changes

NOTE this PR will only merge when 2.0 is available

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: cdoan1 To complete the pull request process, please assign You can assign the PR to them by writing /assign in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files: - **[OWNERS](https://github.com/open-cluster-management/deploy/blob/master/OWNERS)** Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[jnpacker]

Did this code path work for you? I found that the policy was not setting the priority, which cause the Front End pods to fail? I was on snapshot: 2.0.0-SNAPSHOT-2020-07-13-20-00-43

[cdoan1]

@jnpacker everything installed, but the frontend pods did not start--seems the scc did not apply and pods could not run as the user.

[jnpacker]

technically you can edit the SCC on the managed cluster, set priority to 10 and quickly delete the pods and they will provision. But policy eventually switches priority back to null. Which is fine once the pods have started, but they won't restart

[cdoan1]

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.128.2.29. Set the 'ServerName' directive globally to suppress this message
(13)Permission denied: AH00072: make_sock: could not bind to address [::]:80
(13)Permission denied: AH00072: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
AH00015: Unable to open logs

Ok, let me try the workaround. Currently, I have this:

[cdoan1]

seems my anyuid has the right priority 10