You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(validation): Add MicroK8s firewall validation tests for egress a… (#94)
* feat(validation): Add MicroK8s firewall validation tests for egress and pod-to-pod communication
- Implemented `ValidateMicroK8sFirewallAllowsEgress` to test egress connectivity from MicroK8s pods.
- Implemented `ValidateMicroK8sFirewallAllowsPodToPodCommunication` to verify communication between MicroK8s pods.
- Updated validation suite to include new tests for MicroK8s firewall rules.
* refactor(validation): Simplify MicroK8s firewall validation by extracting tests into dedicated functions
- Removed inline tests for MicroK8s firewall egress and pod-to-pod communication from the validation suite.
- Introduced `runMicroK8sFirewallValidation` function to encapsulate MicroK8s firewall tests.
- Enhanced readability and maintainability of the validation code.
* refactor: modify tests to fit rest of format
* fix: remove IP tables fix for testing
* fix: focus the iptables for shadeform
* fix(validation): Remove unnecessary blank line in MicroK8s firewall validation tests
* refactor(validation): Extract firewall validation tests into dedicated function
- Introduced `runFirewallSubtests` to encapsulate firewall-related validation tests for improved readability and maintainability.
- Removed inline firewall tests from `RunInstanceLifecycleValidation` and `RunFirewallValidation` functions.
- Ensured consistent testing structure across different validation scenarios.
* refactor(validation): Update parameter order in runFirewallSubtests for consistency
- Changed the parameter order in `runFirewallSubtests` to place context first, aligning with common Go practices.
- Updated all calls to `runFirewallSubtests` to reflect the new parameter order, enhancing code readability and maintainability.
* feat(validation): Enhance MicroK8s service readiness checks and installation retries
- Added a command to wait for MicroK8s Nginx service endpoints to be ready before proceeding with tests, preventing race conditions.
- Implemented a retry mechanism for the MicroK8s installation process, allowing up to three attempts with delays between retries for improved reliability.
- Included a check to wait for CoreDNS pods to be ready, ensuring subsequent commands relying on DNS resolution do not fail.
* fix: revert the retries. Didn't help nebius
* fix: enable the iptables changes to fix egress
require.NoError(t, err, "ValidateDockerFirewallAllowsContainerToContainerCommunication should pass - container to container communication should be allowed")
require.NoError(t, err, "ValidateDockerFirewallAllowsContainerToContainerCommunication should pass - container to container communication should be allowed")
require.NoError(t, err, "ValidateDockerFirewallAllowsContainerToContainerCommunication should pass - container to container communication should be allowed")
0 commit comments