support thoth production deployment

[harshad16]

Related-To: thoth-station/thoth-application#709
Depends-On: thoth-station/thoth-application#712

support thoth production deployment
Signed-off-by: Harshad Reddy Nalla hnalla@redhat.com

[HumairAK]

/hold

[4n4nd]

@harshad16 @HumairAK would it make sense to separate these components by namespace?
i.e. keep an individual kustomization.yaml for each namespace?

[harshad16]

would it make sense to separate these components by namespace?
i.e. keep an individual kustomization.yaml for each namespace?

As its all thoth component, it is moved to thoth directory.
creating more sub-directory just feels more manual work, would it provide any additional value?

[4n4nd]

would it provide any additional value?

would just make it look cleaner

[harshad16]

would just make it look cleaner

If it is not a requirement from the operate-first side then I would like to keep it this way, as it becomes easier for me(as a users) to check on what's missing.
if I move apps into more sub-directory, then the places to verify would grow with more number of Kustomization.yaml
checking everywhere if the resources are set or not.

[HumairAK]

it's not a requirement, organization of your team's sub folder is up to the team

[HumairAK]

/unhold

[sesheta]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: HumairAK

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [HumairAK]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment