generated from juliaaano/showroom-content
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
17 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Notes | ||
|
||
Using this folder to hold notes about the lab environment that do no belong in the lab materials. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
# Disabling Autosync | ||
|
||
1. Disable Autosync on `bootstrap` inside of the main Gitops | ||
2. Edit `ApplicationSet/tenants` on the openshift-gitops namespace to turn off autosync | ||
1. `oc patch applicationset tenants --type='merge' -p '{"spec": {"template": {"spec": {"syncPolicy": {"automated": {"selfHeal": false}}}}}}' -n openshift-gitops` | ||
3. Disalbe Autosync on `composer-ai-config` | ||
4. Then you should be able to disable autosync on any of the other composer items |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
# Issues and Fixes | ||
|
||
A list of possible known issues and fixes | ||
|
||
## ElasticSearch Issue | ||
|
||
Rarely the elastic search install will run into errors figuring out who is the main node. Easiest way to fix this is delete the entire `Elasticsearch` kubernetes object and let the Argo Recreate, then rerun the ingestion pipeline. |