-
Notifications
You must be signed in to change notification settings - Fork 23
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
Road to a supported installation #27
Comments
after talking to @cirocosta this morning, the steps that we should take are as follows:
@scottietremendous wdyt? |
Extra things to think about: (not for hush-house GA but might be useful)
|
I tend to think we should just go with the repo for incident reporting since that's what we basically do now with Wings. On the second note, I think we should try out as many new features that helm can provide us as possible. I think it's important we still use this as a place to experiment. |
Apologies for acting as some random dude interjecting my opinion here, but I'd gently suggest reconsidering. Thoughts:
3.1. Dogfooding the "environment promotion" workflow is beneficial because it helps drive out optimizations for declarative configuration that can be statically defined in a helm thanks for listening to my dissertation 👍 |
Hey @aegershman, thanks for the thoughtful comment. It makes a lot of sense 👍.
|
Hey @YoussB , In case we end up going with using namespaced secrets as a way of leveraging k8s cred mgmt, we'd need this one tackled first concourse/docs#96 so that we can give a reference for the teams who end up consuming it. Thanks! |
makes sense 👍 |
Hey,
Below is a list of items that we will need to complete/confirm before we can start moving/adding workloads onto hush house:
hush-house
in PKS wouldn't give the team much more data than we'd get from GKE, where we already have it running, allowing us to not have to learn any details of PKS and just move directly to what we already have.concourse-ci.org
topivotal.io
and update certificates #25Thanks!
cc @scottietremendous
The text was updated successfully, but these errors were encountered: