Skip to content

Conversation

@zhiying-lin
Copy link
Contributor

What type of PR is this?
/kind feature

What this PR does / why we need it:
It can used by the default webhook or the profile controller.

Which issue(s) this PR fixes:

Fixes #

Requirements:

How has this code been tested

add unit tests

Special notes for your reviewer

@codecov
Copy link

codecov bot commented Sep 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.68%. Comparing base (e3743e8) to head (82a2d64).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #196      +/-   ##
==========================================
+ Coverage   78.64%   78.68%   +0.03%     
==========================================
  Files          22       23       +1     
  Lines        2210     2228      +18     
==========================================
+ Hits         1738     1753      +15     
- Misses        343      345       +2     
- Partials      129      130       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jwtty jwtty merged commit 2398ebb into Azure:main Sep 13, 2024
@zhiying-lin zhiying-lin deleted the defaulter branch September 13, 2024 07:23
// If no Timeout value is specified, it uses a default value of 9 seconds.
// Reference link: https://learn.microsoft.com/en-us/azure/traffic-manager/traffic-manager-monitoring#configure-endpoint-monitoring
if obj.Spec.MonitorConfig.TimeoutInSeconds == nil {
if *obj.Spec.MonitorConfig.IntervalInSeconds == 30 {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what if the internal in seconds is more than 30?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can specify two values here: 30 seconds (normal probing) and 10 seconds (fast probing) for the intervalInSeconds.

My bad, i thought validation webhook would be invoked first. Will fix it in my next PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants