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

create K8s secrets resources for stage/prod #463

Closed
bookshelfdave opened this issue Sep 7, 2017 · 4 comments
Closed

create K8s secrets resources for stage/prod #463

bookshelfdave opened this issue Sep 7, 2017 · 4 comments
Assignees

Comments

@bookshelfdave
Copy link
Contributor

bookshelfdave commented Sep 7, 2017

we'll need to split out secrets so they don't need to be deployed with each Jenkins deployment.

@bookshelfdave bookshelfdave created this issue from a note in MDN AWS Migration (Queued (Max 6)) Sep 7, 2017
@bookshelfdave bookshelfdave added this to the MDN AWS hosting milestone Sep 7, 2017
@bookshelfdave
Copy link
Contributor Author

@escattone this just hit me this morning, we'll need to create secrets for all the stage/prod environment vars so we can create those once and then let Jenkins push new deployments.

@escattone
Copy link
Contributor

@metadave That's a good point! It doesn't make sense to have to deploy the secrets each time.

@bookshelfdave bookshelfdave moved this from Queued (Max 6) to In Progress (Max 6) in MDN AWS Migration Sep 7, 2017
@bookshelfdave bookshelfdave self-assigned this Sep 7, 2017
@bookshelfdave
Copy link
Contributor Author

I'm thinking of how Jenkins will work, I don't think we can have an unlocked mdn-k8s-private repo on the Jenkins server to populate the secrets on each push. The secrets can be stored and deployed once from mdn-k8s-private.

@bookshelfdave
Copy link
Contributor Author

#467

@bookshelfdave bookshelfdave moved this from In Progress (Max 6) to Review in MDN AWS Migration Sep 8, 2017
@bookshelfdave bookshelfdave moved this from Review to Complete in MDN AWS Migration Sep 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

2 participants