fix dashboard availability check

[pranavcracker]

Description

Dashboard Availability check (TC 208) fails on clusters with authentication enabled (oauth2-proxy + Keycloak). The ingress check strictly expects HTTP 200, but the redirect chain ends with 405 from Keycloak rejecting curl's HEAD request, causing a false negative.

Solution

Updated ingress http_code check in kubernetes_dashboard_status to accept ('200', '405') instead of == '200'

How to apply

NA

Test Cases

TestCase 1

Test Configuration:

• OS: Ubuntu 22.04 LTS
• Inventory: kubernetes-dashboard with oauth2-proxy + Keycloak authentication enabled

Steps:

1. Run kubemarine check_paas --tasks kubernetes.plugins.dashboard

Results:

Before	After
TC 208 FAIL: Dashboard ingress is not running yet...	TC 208 PASS: available

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• There is no breaking changes, or migration patch is provided
• Integration CI passed
• Unit tests. If Yes list of new/changed tests with brief description
• There is no merge conflicts

Unit tests

N/A