-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Add Kubernetes service registration #8249
Merged
Merged
Changes from 2 commits
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
2dc736e
add kubernetes service registration
tyrannosaurus-becks 4dc0d00
rename env vars
tyrannosaurus-becks e75fe3b
increase commentary around env vars
tyrannosaurus-becks c211b87
improve err and comments
tyrannosaurus-becks 708306b
strip onShutdown method
tyrannosaurus-becks f38381e
use io.Reader in NewCertPool
tyrannosaurus-becks c116c5b
minor changes from feedback
tyrannosaurus-becks 38723df
Update serviceregistration/kubernetes/client/client.go
tyrannosaurus-becks 27ec6f4
Update serviceregistration/kubernetes/retry_handler.go
tyrannosaurus-becks 84cd8ec
leave patchesToRetry nil
tyrannosaurus-becks 74c438e
simplify PatchOperation enum to string
tyrannosaurus-becks b00a0c4
use retryable client for exp backoff and jitter
tyrannosaurus-becks 283ba7f
add ability to respond to application stops
tyrannosaurus-becks e92f716
replace toString with FormatBool
tyrannosaurus-becks 511de33
update vendored files
tyrannosaurus-becks 03573a8
stop ticker in retryHandler
tyrannosaurus-becks a89bc1f
update how test fails
tyrannosaurus-becks 662c272
strip req and resp body from error responses
tyrannosaurus-becks 04bc995
use a map to de-dupe patches to same path
tyrannosaurus-becks 630f180
use simpler context
tyrannosaurus-becks 59b3db7
update certutil test
tyrannosaurus-becks e2a0a7b
fix env vars in manual testing doc
tyrannosaurus-becks 255e113
Update serviceregistration/kubernetes/testing/README.md
tyrannosaurus-becks aa1b492
Update serviceregistration/kubernetes/testing/README.md
tyrannosaurus-becks 14ba35f
retry initial state if it fails
tyrannosaurus-becks 8b62a65
improve logging in retry handler
tyrannosaurus-becks 5eb0567
protect against nil response
tyrannosaurus-becks File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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 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 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a technical reason we don't support dev mode? Do we have any other configurations that don't work in dev mode?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mjarmy or @briankassouf do you happen to know the answer to this?
@jasonodonnell , I don't know the original reason for this, but I do know that Consul currently also has service registration and it presently is only available in HA. Right here, it builds how it's going to advertise itself based on whether it's a performance standby. If we were going to make service registration available in wider circumstances, I'm not sure if that could negatively impact Consul from a backwards-compatibility standpoint.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, when I re-read this, I see the question is about dev mode, not HA. I just was thinking about HA because we'd talked about it previously.
In response to the actual question :-), I'd bet that we weren't allowed to run service registrations unless in HA mode because some of the service registration notifications only work with HA. However, this made it difficult to do just little quick tests that didn't pertain to the HA notifications. So I added a flag to allow us to test service registration if the
-dev
flag is included just to make my life a little easier. With this exception added here, I can just do a quick test without running in a clustered mode, or even if I've dropped one single Vault instance into a container. I figured that since it doesn't effect end users, should be fine.