JsonObject ratings = ratingsResponse.getJsonObject("ratings");
            if (ratings.containsKey("Reviewer1")){
          	  starsReviewer1 = ratings.getInt("Reviewer1");
            }
            if (ratings.containsKey("Reviewer2")){
              starsReviewer2 = ratings.getInt("Reviewer2");
            }
          }
        }
      }

                  }
                  var result = {
                      id: productId,
                      ratings: {
                          Reviewer1: firstRating,
                          Reviewer2: secondRating
                      }
                  }
                  res.writeHead(200, {'Content-type': 'application/json'})
                  res.end(JSON.stringify(result))

    export SLEEP_POD=$(kubectl get pod -l app=sleep -o jsonpath={.items..metadata.name})
    kubectl exec -it $SLEEP_POD -c sleep -- curl http://ratings.default.svc.cluster.local:9080/ratings/1
    {"id":1,"ratings":{"Reviewer1":5,"Reviewer2":4}}
    ```

You can also use the sleep service to test accessing services outside of the mesh.

    console.log(pr_resp);
    throw `PR:{pr_number} needs to be valid and closed (merged)`;
  }
  const pr_title = pr_resp.data.title;
  // Assign to PR owner and reviewers
  const assignees = pr_resp.data.assignees.concat(pr_resp.data.requested_reviewers);
  let assignee_logins = assignees.map(x => x.login);
  assignee_logins.push(pr_resp.data.user.login);
  console.log(assignee_logins);

                        break
        for reviewer in pr_reviewers:
            reviewers[reviewer] += 1
        if pr.state == "MERGED" and pr.author:
            contributors[pr.author.login] += 1
    return ContributorsResults(
        contributors=contributors,
        commenters=commenters,
        reviewers=reviewers,
        translation_reviewers=translation_reviewers,
        authors=authors,

versions or groups without other changes, it is OK for your API reviewer to make an
exception.

If you're removing violations from the exception list, or if you have good
reasons to add new violations to this list, please update the file using:

 - `UPDATE_API_KNOWN_VIOLATIONS=true ./hack/update-codegen.sh`

It is up to API reviewers to review the list and make sure new APIs follow our API conventions.

    - enj
    - mikedanese
  sig-cli-api-reviewers:
    - pwittrock
    - soltysh
  sig-cloud-provider-api-reviewers:
    - andrewsykim
    - cheftako
    - dims
  # sig-cluster-lifecycle-api-reviewers:
  #   -
  #   -
  sig-contributor-experience-approvers:
    - mrbobbytables
    - cblecker
    - nikhita
    - palnabarun
    - kaslin
    - MadhavJivrajani
    - Priyankasaggu11929

# See the OWNERS docs at https://go.k8s.io/owners

# approval on api packages bubbles to api-approvers
reviewers:
  - sig-apps-reviewers
  - sig-auth-policy-approvers
  - sig-auth-policy-reviewers
labels:
  - sig/auth

# See the OWNERS docs at https://go.k8s.io/owners

reviewers:
  - sig-network-reviewers
  - sig-node-reviewers
approvers:
  - sig-network-approvers

# See the OWNERS docs at https://go.k8s.io/owners

approvers:
  - api-approvers
reviewers:
  - api-reviewers
  - sig-scheduling-api-reviewers
  - sig-scheduling-api-approvers
labels:
  - kind/api-change