cni-calico-deep integration test is broken
#11567
Comments
alpeb
changed the title
cni-calico-deep integration cluster is brokencni-calico-deep integration test is broken
alpeb
added a commit
that referenced
this issue
Nov 15, 2023
Fixes #11567 The trick is to run the test under k8s `v1.27.6-k3s1` as the following versions break Calico in k3s (see k3d-io/k3d#1375). Also removed the `continue-on-error: true` directive in the integration workflow because it was hiding this problem.
alpeb
added a commit
that referenced
this issue
Nov 17, 2023
Fixes #11567 The trick is to run the test under k8s `v1.27.6-k3s1` as the following versions break Calico in k3s (see k3d-io/k3d#1375). Also removed the `continue-on-error: true` directive in the integration workflow because it was hiding this problem.
alpeb
added a commit
that referenced
this issue
Nov 20, 2023
* Reenable cni-calico-deep integration test Fixes #11567 The trick is to run the test under k8s `v1.27.6-k3s1` as the following versions break Calico in k3s (see k3d-io/k3d#1375). Also removed the `continue-on-error: true` directive in the integration workflow because it was hiding this problem.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
calico-nodepod is failing after a few seconds it starts running. We are using these manifests that are pointed out in k3d docs. They point to a few old image tags, but just updating the tags doesn't work as apparently the manifests need to be updated as well. This started occurring out of the blue, with no changes on our side that appear to have triggered the issue. Probably an upgrade on the github runner that's surfacing an incompatibility.Example of failure:
https://github.com/linkerd/linkerd2/actions/runs/6744688204/job/18335405486
The text was updated successfully, but these errors were encountered: