microsoft / microsoft/Microsoft-Defender-For-Containers
Connectivity Test Script is not getting a 20X
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
While trying to reach the public cloud endpoint, I am getting a 404 error:
Script: connectivity_test.sh
Command used:
./def_conn_test.sh public
Output:
Target Cloud: Public
Endpoint: https://api.cloud.defender.microsoft.com/api/connectivity/v1/
job.batch/curl-connectivity-public-1773657230 created
Waiting for job to complete...
error: timed out waiting for the condition on jobs/curl-connectivity-public-1773657230
Job failed, timed out, or endpoint unreachable.
--- Job Logs ---
Connectivity to Public failed (404)
Cleaning up job...
job.batch "curl-connectivity-public-1773657230" deleted from default namespace
Manual test from my Laptop:
curl -s -o /dev/null -w "%{http_code}" https://api.cloud.defender.microsoft.com/api/connectivity/v1/
404
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with scripts/connectivity_test.sh and reproduce the reported ./def_conn_test.sh public command, then compare its Kubernetes job output with the manual curl response for the listed endpoint. Confirm the cause of the 404 and timeout, and document or correct the connectivity test so its result matches the endpoint's expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, shell
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100