Refactor DNS name extraction #13
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Nov 29, 2024
tjamet
force-pushed
the
maiao.I46f513341ce01ec6e9d67897c6d0cb58aeec3021
branch
from
cdf930a to
d1b3f8e
Compare
tjamet
force-pushed
the
maiao.I5f01e93edd2b8c48689588a871905047d4fbed8f
branch
from
832eea3 to
c76cc2b
Compare
Fsero
approved these changes
Nov 29, 2024
tjamet
force-pushed
the
maiao.I46f513341ce01ec6e9d67897c6d0cb58aeec3021
branch
from
d1b3f8e to
e598f58
Compare
tjamet
force-pushed
the
maiao.I5f01e93edd2b8c48689588a871905047d4fbed8f
branch
from
c76cc2b to
12cac70
Compare
miguelbernadi
approved these changes
Dec 10, 2024
tjamet
force-pushed
the
maiao.I5f01e93edd2b8c48689588a871905047d4fbed8f
branch
from
12cac70 to
85493fe
Compare
tjamet
force-pushed
the
maiao.I46f513341ce01ec6e9d67897c6d0cb58aeec3021
branch
2 times, most recently
from
47d866c to
bd4c585
Compare
tjamet
force-pushed
the
maiao.I5f01e93edd2b8c48689588a871905047d4fbed8f
branch
2 times, most recently
from
b07a195 to
a64daca
Compare
tjamet
force-pushed
the
maiao.I46f513341ce01ec6e9d67897c6d0cb58aeec3021
branch
from
bd4c585 to
4b17c88
Compare
tjamet
force-pushed
the
maiao.I46f513341ce01ec6e9d67897c6d0cb58aeec3021
branch
from
4b17c88 to
e23b773
Compare
tjamet
force-pushed
the
maiao.I5f01e93edd2b8c48689588a871905047d4fbed8f
branch
from
a64daca to
24a5d90
Compare
tjamet
force-pushed
the
maiao.I46f513341ce01ec6e9d67897c6d0cb58aeec3021
branch
from
e23b773 to
023e6f8
Compare
tjamet
force-pushed
the
maiao.I5f01e93edd2b8c48689588a871905047d4fbed8f
branch
from
24a5d90 to
f7aeef7
Compare
Goal --- Ease the implementation of CRD based multi-ingress controller traffic routing Change-Id: I46f513341ce01ec6e9d67897c6d0cb58aeec3021
tjamet
changed the title
tjamet
force-pushed
the
maiao.I46f513341ce01ec6e9d67897c6d0cb58aeec3021
branch
from
023e6f8 to
6f3c338
Compare
tjamet
changed the base branch from
maiao.I5f01e93edd2b8c48689588a871905047d4fbed8f
to
main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Goal
Ease the implementation of CRD based multi-ingress controller traffic routing
Committer details
Local-Branch: mainRelated changes
Future changes
Add integration test (#16)
Goal ---Ensure that the chart provides enough privileges for the controller to work
Add fine-grain ingress DNS control through CRD (#14)
Context ---Handling usual cluster operations, we often come to operate higher risk changes like bumping ingress controller
versions, changing the underneath ingress service type (for example moving from an AWS ELB to an AWS NLB).
Doing so, the safest way would be to be able to provision a new ingress controller and progressively migrating traffic
to the new instance.
Problems
Currently, traffic controller reads the host and load balancer reference using
the ingress status.
This prevents from being able to handle and control weighted records across the different ingress controllers.
Goal
Enable fine-grained routing between various ingress controllers in the same cluster.
Unblocked use-cases