-
Notifications
You must be signed in to change notification settings - Fork 65
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
Remove all config generation in the deployer #1925
Comments
5 tasks
yuvipanda
added a commit
to yuvipanda/pilot-hubs
that referenced
this issue
Nov 16, 2022
We purely use ingress for HTTPS everywhere, so this is a noop. Ref 2i2c-org#1925
yuvipanda
added a commit
to yuvipanda/pilot-hubs
that referenced
this issue
Nov 16, 2022
This was referenced Nov 16, 2022
yuvipanda
added a commit
to yuvipanda/pilot-hubs
that referenced
this issue
Nov 16, 2022
yuvipanda
added a commit
to yuvipanda/pilot-hubs
that referenced
this issue
Nov 16, 2022
yuvipanda
added a commit
to yuvipanda/pilot-hubs
that referenced
this issue
Nov 16, 2022
yuvipanda
added a commit
to yuvipanda/pilot-hubs
that referenced
this issue
Nov 16, 2022
damianavila
moved this from Ready to work
to In progress
in DEPRECATED Engineering and Product Backlog
Nov 23, 2022
3 tasks
github-project-automation
bot
moved this from In progress
to Complete
in DEPRECATED Engineering and Product Backlog
Mar 24, 2023
Just absolutely amazing work, @GeorgianaElena!!!!!!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From a right to replicate perspective, our end users should be able to take the config out of this repo, and be able to use a
helm
command to continue to deploy the hubs, passing in just the config. The current impediment to this is the bits of config we autogenerate from the deployer:infrastructure/deployer/hub.py
Line 27 in e351ddd
TODO:
The text was updated successfully, but these errors were encountered: