Skip to content
Linting

E2E: use ServiceDiscovery CR to determine if clusterset IP is enabled #2629

Sign in to view logs

E2E: use ServiceDiscovery CR to determine if clusterset IP is enabled

E2E: use ServiceDiscovery CR to determine if clusterset IP is enabled #2629

Triggered via pull request October 1, 2024 17:57
@tpantelistpantelis
synchronize #1653
vthapar:clustersetip-e2e-fix
Status Success
Total duration 3m 39s
Artifacts –

linting.yml

on: pull_request
No "Apply suggestions from code review" Commits
3s
No "Apply suggestions from code review" Commits
Commit Message(s)
11s
Commit Message(s)
Go
2m 49s
Go
Dependency Licenses
3m 26s
Dependency Licenses
Markdown Links (modified files)
18s
Markdown Links (modified files)
Markdown
15s
Markdown
Package Documentation
31s
Package Documentation
Vulnerability Scanning
27s
Vulnerability Scanning
YAML
8s
YAML
Fit to window
Zoom out
Zoom in

Annotations

1 warning
No "Apply suggestions from code review" Commits
The following actions use a deprecated Node.js version and will be forced to run on node20: tim-actions/get-pr-commits@198af03565609bb4ed924d1260247b4881f09e7d, tim-actions/commit-message-checker-with-regex@094fc16ff83d04e2ec73edb5eaf6aa267db33791. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/