Skip to content

Hostname allowconnection nft fix - #302

Open
MykolaSuperman wants to merge 2 commits into
aosedge:developfrom
MykolaSuperman:hostname-allowconnection-nft-fix
Open

MykolaSuperman wants to merge 2 commits into
aosedge:developfrom
MykolaSuperman:hostname-allowconnection-nft-fix

Conversation

@MykolaSuperman

Copy link
Copy Markdown

No description provided.

@MykolaSuperman
MykolaSuperman changed the base branch from main to develop September 10, 2026 13:47
@MykolaSuperman
MykolaSuperman force-pushed the hostname-allowconnection-nft-fix branch 2 times, most recently from 686d267 to bcf5662 Compare September 26, 2026 05:35
Mykola Solianko added 2 commits September 26, 2026 09:43
Keep item ID precedence, persist instance hostnames and resolve pending hostname connections. Add database migration and regression tests.

Signed-off-by: Mykola Solianko <mykola_solianko@epam.com>
Separate ingress and egress checks while preserving same-subnet access. Restrict public access to destinations outside AoS pools and retain batch handle caching. Add firewall regression and kernel tests.

Signed-off-by: Mykola Solianko <mykola_solianko@epam.com>
@MykolaSuperman
MykolaSuperman force-pushed the hostname-allowconnection-nft-fix branch from bcf5662 to 781ed55 Compare September 27, 2026 06:07
@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
36.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant