This repository has been archived by the owner on May 31, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TL;DR
I think this used to work because the flyte binary used to run as a process inside the top level container. Now it runs in the cluster. In order for K8s to call out the the webhook service (which in the
--dev
case is running on the user's host machine), we need to pipe through the host machine's IP.This works in conjunction with flyteorg/flyte#3228.
This has been tested with both the
--dev
switch and without it.Type
Are all requirements met?
Complete description
The extra hosts was first added in #369. At the time the flyte binary ran as a process in the dind container. I guess at that time, K8s was able to see the dind container as 127.0.0.1, and so routing there would hit the flyte binary.
Tracking Issue
flyteorg/flyte#3080