mirror of
https://github.com/PurpleComputing/scim-examples.git
synced 2026-06-11 07:10:30 +01:00
Updating readme
signed Updating readme to include details of an error a person might encounter when applying a deployment from the same directory as the workspace json files so they can self-troubleshoot. Co-Authored-By: Adam Pike <adam.pike@1password.com>
This commit is contained in:
@@ -75,6 +75,13 @@ Run the following command deploy SCIM bridge:
|
||||
kubectl apply -f .
|
||||
```
|
||||
|
||||
If you store your workspace-credentials.json and workspace-settings.json files in the same directory as your deployment files, you may see the following error after runing `kubectl apply -f .` below:
|
||||
```
|
||||
error validating "workspace-credentials.json": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
|
||||
error validating "workspace-settings.json": error validating data: [apiVersion not set, kind not set]; if you choose to ignore these errors, turn validation off with --validate=false
|
||||
```
|
||||
You can safely ignore these errors, or move the workspace-credentials.json and workspace-settings.json to a different directory when running `kubectl apply -f .`.
|
||||
|
||||
## Create the DNS record
|
||||
|
||||
The [`op-scim-bridge` Service](./op-scim-service.yaml) creates a public load balancer attached to your cluster that forwards TLS traffic to SCIM bridge.
|
||||
|
||||
Reference in New Issue
Block a user