-
Notifications
You must be signed in to change notification settings - Fork 18
Commit
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -95,6 +95,7 @@ porter credentials generate porterops -r ghcr.io/getporter/porter-operator:v0.8. | |
``` | ||
|
||
Install the operator into the porter-operator-system namespace: | ||
* NOTE: Use your custom namespace if you want to install to a different one by adding **--param operatorNamespace=your-namespace-name** | ||
This comment has been minimized.
Sorry, something went wrong.
carolynvs
Member
|
||
``` | ||
porter install porterops -c porterops -r ghcr.io/getporter/porter-operator:v0.8.0 | ||
``` | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -40,7 +40,7 @@ The bundle includes a custom action that prepares a namespace for you: | |
porter invoke porterops --action configureNamespace --param namespace=quickstart -c porterops | ||
``` | ||
|
||
The Porter Operator is now installed on your cluster in the porter-operator-system namespace, along with a Mongodb server. | ||
The Porter Operator is now installed on your cluster in the porter-operator-system (or your custom namespace) namespace, along with a Mongodb server. | ||
This comment has been minimized.
Sorry, something went wrong.
carolynvs
Member
|
||
This database is not secured with a username/password, so do not use this default installation configuration with production secrets! | ||
The cluster has a namespace, quickstart, where we will create resources and Porter will create jobs to run Porter. | ||
|
||
|
@@ -50,6 +50,7 @@ Let's update your local porter CLI to read the data from the operator's datastor | |
This isn't necessary for the operator to work, but will allow us to see what's happening and understand how the operator works. | ||
|
||
Run the following command to expose the operator's mongodb server to your localhost: | ||
* NOTE: Use your custom namespace if you have installed with the non-default one (porter-operator-system) | ||
``` | ||
kubectl port-forward --namespace porter-operator-system svc/mongodb 27020:27017 >/dev/null & | ||
``` | ||
|
config.Namespace is the namespace where the AgentConfig CRD is defined, and isn't the value we want to use to determine the operator's namespace.
This controller is always going to run in the namespace where the operator was installed. So what we need to do is lookup the current namespace from inside the operator pod. I believe we can read this information directly from
/var/run/secrets/kubernetes.io/serviceaccount/namespace
when we start and then remember it in memory so that we don't need to look it up each time.