-
Notifications
You must be signed in to change notification settings - Fork 38
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
fix: Add --port argument in flagd pods for set flagd service port #710
base: main
Are you sure you want to change the base?
fix: Add --port argument in flagd pods for set flagd service port #710
Conversation
3376172
to
07146d9
Compare
Signed-off-by: kimsehwan96 <sktpghks138@gmail.com> Add missed mock Ports in flagdinjector_test.go getExpectedPod Signed-off-by: kimsehwan96 <sktpghks138@gmail.com> Change wrong container port name port into flagd
07146d9
to
c47d623
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #710 +/- ##
==========================================
+ Coverage 86.51% 87.10% +0.58%
==========================================
Files 19 19
Lines 1587 1326 -261
==========================================
- Hits 1373 1155 -218
+ Misses 173 128 -45
- Partials 41 43 +2
... and 17 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more. |
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.
This should be set by the environment variable, but it looks like the "FLAGD" prefix is missing. I'm in favor of setting the CLI flags even more explicitly, but it would be good to understand why the environment variables aren't working properly.
@beeme1mr |
This PR
--port
with FeatureFlagSoruce configuration)Related Issues
Fixes #709
Notes
Follow-up Tasks
I don't have the background knowledge of why this feature wasn't implemented, and I haven't tested this code, so a thorough PR review is needed
How to test
Set
FeatureFlagSource.spec.port
with specific number and check the--port
argument was properly set and check its debug log atinfo flag-evaluation/connect_service.go:227 Flag IResolver listening at: {PORT_NUMBER}