Run instances with IMDSv2
What critical bug this MR is fixing?
Closes #15 (closed)
How does this change help reduce cost of usage? What scale of cost reduction is it?
In what scenarios is this change usable with GitLab Runner's docker+machine executor?
Merge request reports
Activity
mentioned in issue #15 (closed)
assigned to @tmaczukin
- Resolved by Thiago Presa
- Resolved by Thiago Presa
- Resolved by Thiago Presa
- Resolved by Thiago Presa
- Resolved by Thiago Presa
@tpresa Back to you with my comments
assigned to @tpresa and unassigned @tmaczukin
added 5 commits
-
8a983a19...ab64f7c2 - 3 commits from branch
master
- 6de1ec3b - WIP: Run instances with IMDSv2
- a41dec94 - First review round
-
8a983a19...ab64f7c2 - 3 commits from branch
marked this merge request as draft from 6de1ec3b
assigned to @tmaczukin and unassigned @tpresa
- Resolved by Tomasz Maczukin
@tpresa Can you squash the commits to one? There is no reason to have a "some updates" type of commit in the history and given the nature of this fork we try to have as less commits as possible
assigned to @tpresa and unassigned @tmaczukin
assigned to @tmaczukin and unassigned @tpresa
Thanks for handling this @tpresa! Thanks for the merge @tmaczukin. :)
mentioned in issue gitlab-org/gitlab#334160
mentioned in issue gitlab-org/gitlab-runner#28027
mentioned in issue #93