Revert PR #1: Garcia/change to operator (#18)

Author: andywgarcia

README.md

@@ -4,14 +4,14 @@ This repository contains a reference architecture utilizing [Kubernetes](https:/
 
 Once the architecture is fully stood up, you'll have: 
 
-- An Apollo Router running and managed by the [Apollo GraphOS Operator](https://www.apollographql.com/docs/apollo-operator/), utilizing:
+- An Apollo Router running utilizing:
   - [Persisted Queries for safelisting operations](https://www.apollographql.com/docs/router/configuration/persisted-queries/#differences-from-automatic-persisted-queries)
   - [A coprocessor for handling customizations outside of the router](https://www.apollographql.com/docs/router/customizations/coprocessor)
   - [Rhai scripts to do basic customizations within the router container](https://www.apollographql.com/docs/router/customizations/rhai)
   - [Authorization/Authentication directives](https://www.apollographql.com/docs/router/configuration/authorization)
-- Eight subgraphs, each handling a portion of the overall supergraph schema, with schemas automatically published to GraphOS via the operator
+- Eight subgraphs, each handling a portion of the overall supergraph schema
 - A React-based frontend application utilizing Apollo Client
-- Apollo GraphOS Operator for automated schema publishing, composition, and deployment
+- GitHub Actions to automate image building and GraphOS-specific implementations, including schema publishing and persisted query manifest creation/publishing
 - Tools to run k6 load tests against the architecture from within the same cluster
 
 ### The ending architecture
@@ -45,14 +45,6 @@ During setup, you'll be:
 - Provisioning resources
 - Deploying the applications, including router, subgraphs, client, and observability tools
 
-### [Operator Guide](/docs/operator-guide.md)
-
-Learn how the Apollo GraphOS Operator works in this architecture, including:
-- Schema publishing and composition flow
-- Monitoring operator-managed resources
-- Troubleshooting common issues
-- Updating router configuration
-
 ### [Cleanup](/docs/cleanup.md)
 
 Once finished, you can cleanup your environments following the above document.

deploy/client/values.yaml

@@ -1,7 +1,7 @@
 replicaCount: 3
 
 image:
-  repository: ghcr.io/${GITHUB_ORG}/reference-architecture/client
+  repository: ghcr.io/apollosolutions/reference-architecture/client
   pullPolicy: Always
   tag: main
 

deploy/coprocessor/values.yaml

@@ -1,9 +1,7 @@
-namespace: apollo
-
 replicaCount: 3
 
 image:
-  repository: ghcr.io/${GITHUB_ORG}/reference-architecture/coprocessor
+  repository: ghcr.io/apollosolutions/reference-architecture/coprocessor
   pullPolicy: Always
   tag: main