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 MCM repos to internal concourse #755

Open
himanshu-kun opened this issue Sep 27, 2022 · 1 comment
Open

Move MCM repos to internal concourse #755

himanshu-kun opened this issue Sep 27, 2022 · 1 comment
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage)

Comments

@himanshu-kun
Copy link

What would you like to be added:
We would like to move MCM repos external pipelines to internal concourse

Why is this needed:
This will

  • helps in dynamic update of infra creadentials for IT
  • helps in writing IT for Openstack
@himanshu-kun himanshu-kun added the kind/enhancement Enhancement, improvement, extension label Sep 27, 2022
@himanshu-kun
Copy link
Author

We had a discussion with @ccwienk @AndreasBurger

Short notes

  • polling would be required to trigger pipeline on head update or PR creation, as currently we don't have access to external github webhooks from internal github
  • arm image build getting stuck can start occuring again on moving to internal as QEMU would be usedThis problem was solved for external concourse by adding ARM nodes, but CCEE doesn't support ARM nodes as of now.
  • A proposed approach is to have two pipelines per pipeline we have today. one will be external which will build the images, and post result somewhere, and then other will be internal which will poll for results and will run IT with the resulted images. Although with the current implementation of IT , we don't use these images , but run directly the code.
  • We need to research more abt prow before we start working on this, because Prow is external only, but has many features.

cc @rishabh-11 @unmarshall

@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Jun 6, 2023
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage)
Projects
None yet
Development

No branches or pull requests

2 participants