Conversation
I'mn hoping this will fix `Unknown` status for `search-service-admin`.
ChatGPT says:
ArgoCD hooks are best used with namespaced resources, because:
ArgoCD tracks resources under .status.resources[], which expects to
resolve:
```
{
"kind": "ClusterExternalSecret",
"namespace": "...",
"name": "search-service",
...
}
```
When you apply argocd.argoproj.io/hook to a cluster-scoped resource, the
namespace field will be "", which causes ArgoCD to generate an invalid
internal representation, specifically in the JSON patch sent to
Kubernetes.
This corrupts .status.resources and causes errors like:
```
Error constructing app status patch: unable to find api field in struct
RawExtension for the json field "spec"
```
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'mn hoping this will fix
Unknownstatus forsearch-service-admin. ChatGPT says:ArgoCD hooks are best used with namespaced resources, because:
ArgoCD tracks resources under .status.resources[], which expects to resolve:
When you apply argocd.argoproj.io/hook to a cluster-scoped resource, the namespace field will be "", which causes ArgoCD to generate an invalid internal representation, specifically in the JSON patch sent to Kubernetes.
This corrupts .status.resources and causes errors like: