Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move deployment manifests to a separate repository #92

Open
larsks opened this issue Mar 24, 2023 · 2 comments
Open

Move deployment manifests to a separate repository #92

larsks opened this issue Mar 24, 2023 · 2 comments

Comments

@larsks
Copy link
Member

larsks commented Mar 24, 2023

We should move the deployment manifests for this application to a separate repository.

Making configuration changes for quotas and limits (e.g., nerc-project/operations#90) should not involve releasing a new version of the application (and if this code ever sees adoption outside of the MOC, it's possible our deployment manifests wouldn't even be appropriate).

@larsks
Copy link
Member Author

larsks commented Mar 24, 2023

Or maybe we just need to move the quota and limit definitions elsewhere? Trying to think of how best to make it simple to update the configuration.

@jtriley
Copy link
Collaborator

jtriley commented Mar 31, 2023

At least for the NERC prod cluster these live in the nerc-ocp-config repo. See: OCP-on-NERC/nerc-ocp-config#225

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants