test(e2e): bump compose-bridge images to v0.0.7 - #14170
Conversation
v0.0.3 had a mis-published multi-arch manifest, causing exec format errors on non-amd64 architectures. Fixed upstream in docker/compose-bridge-transformer@665f67e. Signed-off-by: Ricardo Branco <rbranco@suse.de>
glours
left a comment
There was a problem hiding this comment.
Thank you @ricardobranco777 🙏
Root causeThe Commit Bumping Files to update
Diff--- a/pkg/e2e/fixtures/bridge/expected-kubernetes/base/private-network-network-policy.yaml
+++ b/pkg/e2e/fixtures/bridge/expected-kubernetes/base/private-network-network-policy.yaml
@@ -11,14 +11,8 @@
com.docker.compose.network.private-network: "true"
policyTypes:
- Ingress
- - Egress
ingress:
- from:
- podSelector:
matchLabels:
com.docker.compose.network.private-network: "true"
- egress:
- - to:
- - podSelector:
- matchLabels:
- com.docker.compose.network.private-network: "true"
--- a/pkg/e2e/fixtures/bridge/expected-kubernetes/base/public-network-network-policy.yaml
+++ b/pkg/e2e/fixtures/bridge/expected-kubernetes/base/public-network-network-policy.yaml
@@ -11,14 +11,8 @@
com.docker.compose.network.public-network: "true"
policyTypes:
- Ingress
- - Egress
ingress:
- from:
- podSelector:
matchLabels:
com.docker.compose.network.public-network: "true"
- egress:
- - to:
- - podSelector:
- matchLabels:
- com.docker.compose.network.public-network: "true"
--- a/pkg/e2e/fixtures/bridge/expected-helm/templates/private-network-network-policy.yaml
+++ b/pkg/e2e/fixtures/bridge/expected-helm/templates/private-network-network-policy.yaml
@@ -11,14 +11,8 @@
com.docker.compose.network.private-network: "true"
policyTypes:
- Ingress
- - Egress
ingress:
- from:
- podSelector:
matchLabels:
com.docker.compose.network.private-network: "true"
- egress:
- - to:
- - podSelector:
- matchLabels:
- com.docker.compose.network.private-network: "true"
--- a/pkg/e2e/fixtures/bridge/expected-helm/templates/public-network-network-policy.yaml
+++ b/pkg/e2e/fixtures/bridge/expected-helm/templates/public-network-network-policy.yaml
@@ -11,14 +11,8 @@
com.docker.compose.network.public-network: "true"
policyTypes:
- Ingress
- - Egress
ingress:
- from:
- podSelector:
matchLabels:
com.docker.compose.network.public-network: "true"
- egress:
- - to:
- - podSelector:
- matchLabels:
- com.docker.compose.network.public-network: "true" |
v0.0.6 dropped the Egress policyType/block from generated NetworkPolicy manifests since it blocked CoreDNS traffic; update the fixtures to match. Signed-off-by: Ricardo Branco <rbranco@suse.de>
Head branch was pushed to by a user without write access
Yup. This solved it. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
What I did
v0.0.3 had a mis-published multi-arch manifest, causing exec format errors on non-amd64 architectures.
Fixed upstream in docker/compose-bridge-transformer@665f67e.
Otherwise test fails on openQA: https://openqa.opensuse.org/tests/6193496#external
Related issue
(not mandatory) A picture of a cute animal, if possible in relation to what you did