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

Pipeline automation between EC2 service pipeline and k8s pipeline #328

Closed
robrap opened this issue Jun 12, 2023 · 3 comments
Closed

Pipeline automation between EC2 service pipeline and k8s pipeline #328

robrap opened this issue Jun 12, 2023 · 3 comments
Labels
event-bus Work related to the Event Bus. wontfix This will not be worked on

Comments

@robrap
Copy link
Contributor

robrap commented Jun 12, 2023

Do we need to automate hooking up EC2 pipelines with k8s consumer pipelines, rather than making this manual and having the consumers potentially get out of sync? When will this start causing issues?

@robrap robrap added this to Arch-BOM Jun 12, 2023
@robrap robrap converted this from a draft issue Jun 12, 2023
@robrap robrap added the event-bus Work related to the Event Bus. label Jun 12, 2023
@robrap
Copy link
Contributor Author

robrap commented Jun 16, 2023

Maybe we just ignore this until everything is in k8s?

@robrap
Copy link
Contributor Author

robrap commented Nov 29, 2023

For now, we've continued to put effort toward containerization, rather than into linking the GoCD pipelines. Hopefully dealing with manual deployments of the k8s consumer containers is good enough. If not, we can remove this from the icebox.

@jristau1984 jristau1984 added the wontfix This will not be worked on label Jul 22, 2024
@jristau1984
Copy link

We will be rolling this goal into the containerization effort, so this is no longer needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
event-bus Work related to the Event Bus. wontfix This will not be worked on
Projects
Archived in project
Development

No branches or pull requests

2 participants