You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+15-2Lines changed: 15 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,9 +63,11 @@ spec:
63
63
64
64
## Configuration
65
65
66
+
### Clients
67
+
66
68
The Sandbox operator can leverage different clients, depending upon how authenitcation is configured for your cluster.
67
69
68
-
### Azure
70
+
#### Azure
69
71
70
72
If Azure credentials are provided to the operators environment, it will perform a lookup of each user in the `owners` field and fetch that users `ObjectID` inside of Azure using the [Microsoft Graph API](https://docs.microsoft.com/en-us/graph/api/resources/azure-ad-overview?view=graph-rest-1.0).
71
73
@@ -81,10 +83,21 @@ Your Azure Service Principal will need the following _Application_ permission fo
If no credentials are provided, the operator will create the `Role` and `ClusterRole` bindings using the values listed in the `owners` field.
87
89
90
+
### Docker Pull Secrets
91
+
92
+
By default, the operator will not create any secrets in the provisioned namespace.
93
+
94
+
**If the `PULL_SECRET_NAME` environment variable is set, the operator will copy your clusters pull secret to the provisioned namespace and patch the default service account.**
95
+
96
+
`PULL_SECRET_NAME`should be the name of the pull secret that exists in your cluster. By default, the operator will look for your secret in the `default` namespace.
97
+
98
+
To have the operator look in a different namespace for the pull secret, use the `PULL_SECRET_NAMESPACE` environment variable.
99
+
100
+
88
101
## Creating a Sandbox
89
102
90
103
To create a Sandbox, apply a Sandbox CRD to the target cluster.
0 commit comments