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
To get data about other parts of the cluster (not specific to [gitops-operator](https://github.com/redhat-developer/gitops-operator/)), run `oc adm must-gather` (without passing a custom image).
26
+
Run `oc adm must-gather -h` to see more options.
26
27
27
-
- All executed commands: `must-gather-script-commands.txt`
28
-
- Errors: `must-gather-script-errors.txt`
29
-
- Commands that produced no output: `must-gather-script-no-output.txt`
28
+
## Development
30
29
31
-
All the output of the commands is stored into 3 different formats:
30
+
Make sure you run `make lint` before pushing new changes.
31
+
This requires `shellcheck` to be installed in your machine.
32
+
33
+
For more information about `building` and `pushing` the image, see `make help`.
34
+
35
+
### Image publishing
32
36
33
-
-`*.txt` that represents the normal view without any structure.
34
-
-`*.yaml` that is the YAML output of the command.
35
-
-`*.json` that is the JSON output of the command.
37
+
CD images are pushed to the following destinations, from where they can be used for testing:
36
38
37
-
In order to get data about other parts of the cluster (not specific to gitops-operator) you should run just `oc adm must-gather` (without passing a custom image). Run `oc adm must-gather -h` to see more options.
39
+
- HEAD of the `main` branch: quay.io/redhat-user-workloads/rh-openshift-gitops-tenant/gitops-must-gather:latest
An example of the GitOps must-gather output would be something like the following, where there are two argocd instances in namespaces `openshift-gitops` and `foo` and an additional namespace called `foo-managed` which is managed by namespace `foo`:
# You may need to create the repository on quay.io manually to make sure it is public
47
+
make REGISTRY_USERNAME=my-non-production-org CONTAINER_IMAGE_TAG=latest push
182
48
```
183
-
Note: most of the resource outputs are given in 3 file types: `.json`, `.yaml`, and `.txt`, however those files are combined in this tree for clarity and conciseness.
49
+
It is recomanded to use `latest` tag for development, because it does not get cached on OpenShift nodes - other tags might.
184
50
185
51
## Testing
186
52
187
-
To do that you need an OpenShift cluster, and you will have to install the Red Hat GitOps Operator.
188
-
Then you can test how your changes affects gathered data:
53
+
Create the OpenShift cluster, log in and install the Red Hat GitOps Operator.
189
54
55
+
For the development version, use:
190
56
```shell
191
-
# You may need to create the repository on quay.io manually to make sure it is public
192
-
make REGISTRY_USERNAME=my-non-production-org CONTAINER_IMAGE_TAG="$(git rev-parse HEAD)" push
193
-
# Note some differences are expected, like few lines in rapidly populated logs
0 commit comments