Skip to content
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

feat: create a file to mark that the outbound check is skipped for network isolated cluster feature #5863

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

bingosummer
Copy link
Member

@bingosummer bingosummer commented Feb 18, 2025

What type of PR is this?

/kind feature

What this PR does / why we need it:

When run kubectl describe nodes in a network isolated cluster, we see an EgressBlocked warning. It's sent by the node-problem-detector. This PR creates a file /var/run/outbound-check-skipped to mark that the outbound check is skipped. When the file exists, the node-problem-detector will not send the EgressBlocked warning.

Warning  EgressBlocked                     26m                 node-egress-monitor                                           Required endpoints are unreachable (curl: (28) Failed to connect to mcr.microsoft.com port 443 after 7635 ms: Connection timed out ;curl: (28) Failed to connect to login.microsoftonline.com port 443 after 9964 ms: Connection timed out ;curl: (28) Failed to connect to management.azure.com port 443 after 5204 ms: Connection timed out ;curl: (28) Failed to connect to packages.microsoft.com port 443 after 5203 ms: Connection timed out ;curl: (28) Failed to connect to acs-mirror.azureedge.net port 443 after 7502 ms: Connection timed out: https://acs-mirror.azureedge.net/acs-mirror/healthz ;curl: (28) Connection timed out after 10000 milliseconds: https://packages.aks.azure.com/acs-mirror/healthz ), aka.ms/AArpzy5 for more information.

Which issue(s) this PR fixes:

Fixes #

Requirements:

Special notes for your reviewer:

Release note:

none

@bingosummer bingosummer changed the title create a file to mark that the outbound check is skipped feat: create a file to mark that the outbound check is skipped for network isolated cluster feature Feb 24, 2025
@bingosummer bingosummer force-pushed the binxi/ni-egress-monitor branch from 0fb6d15 to 40f2f54 Compare February 24, 2025 02:58
@bingosummer bingosummer enabled auto-merge (squash) February 24, 2025 10:04
@@ -83,6 +83,9 @@ if [[ -n "${OUTBOUND_COMMAND}" ]]; then
eval $PROXY_VARS
fi
retrycmd_if_failure 50 1 5 $OUTBOUND_COMMAND >> /var/log/azure/cluster-provision-cse-output.log 2>&1 || exit $ERR_OUTBOUND_CONN_FAIL;
else
# This file indicates the cluster doesn't have outbound connectivity and should be excluded in future external outbound checks
touch /var/run/outbound-check-skipped
Copy link
Collaborator

Choose a reason for hiding this comment

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

can we add something to agentbaker e2e to ensure this exists after CSE exits within NI scenarios?

@bingosummer bingosummer merged commit 9296da2 into master Feb 24, 2025
17 checks passed
@bingosummer bingosummer deleted the binxi/ni-egress-monitor branch February 24, 2025 16:14
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.

4 participants