Create ServiceAccount before creating Secret associated with a ServiceAccount

[sethiyash]

Describe the problem/challenge you have
When we create a Secret which is of type service account token, then the ServiceAccount should be created first.
Presently, kapp does not await the creation of the ServiceAccount prior to creating a Secret associated with said ServiceAccount. Consequently, the Secret encounters reconciliation failure, manifesting with the following error message:

kapp: Error: waiting on reconcile secret/amr-access-token (v1) namespace: default:
  Errored:
    Getting resource secret/amr-access-token (v1) namespace: default:
      API server says: secrets "amr-access-token" not found (reason: NotFound)

Describe the solution you'd like
There should be a default rule in kapp to create the service account first before creating a Secret associated with a ServiceAccount

Anything else you would like to add:
[Additional information that will assist in solving the issue.]

---

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

[praveenrewar]

I just realised that we already have an issue present for this.