-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: [CNI] Load testing for cilium cni #1871
Conversation
ab789ce
to
a3ba93c
Compare
517d1d4
to
594b2bf
Compare
95fee90
to
2e26bdb
Compare
39e3de6
to
6f162e1
Compare
please make sure you address/resolve other comments as well |
6f162e1
to
8444ad2
Compare
make -C ./hack/swift set-kubeconf AZCLI=az CLUSTER=${RESOURCE_GROUP} | ||
make -C ./hack/swift azcfg AZCLI=az REGION=$(LOCATION) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't need these to bring the cluster down
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will the context be retained even if the bringing down of the cluster is a part of a different stage ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you might need the azcfg target, but you definitely don't need the kubeconfig
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked removing the set kubeconfig and it failed with:
error: cannot delete cluster cilium-vipul-test, not in /home/vsts/.kube/config
echo "install cilium CLI" | ||
CILIUM_CLI_VERSION=$(curl -s https://raw.githubusercontent.com/cilium/cilium-cli/master/stable.txt) | ||
CLI_ARCH=amd64 | ||
if [ "$(uname -m)" = "aarch64" ]; then CLI_ARCH=arm64; fi | ||
curl -L --fail --remote-name-all https://github.com/cilium/cilium-cli/releases/download/${CILIUM_CLI_VERSION}/cilium-linux-${CLI_ARCH}.tar.gz{,.sha256sum} | ||
sha256sum --check cilium-linux-${CLI_ARCH}.tar.gz.sha256sum | ||
sudo tar xzvfC cilium-linux-${CLI_ARCH}.tar.gz /usr/local/bin | ||
rm cilium-linux-${CLI_ARCH}.tar.gz{,.sha256sum} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
their script needs to be flexible, but we know what arch and version we want - fix all of these variables so that we get the same thing every time
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean hardcode the cli version and arch version ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, we should pin those so that the CI is consistent
6f5eceb
to
a9809a4
Compare
needs rebase |
a9809a4
to
c545c83
Compare
containers: | ||
- name: privileged-container | ||
image: mcr.microsoft.com/dotnet/runtime-deps:6.0 | ||
command: ["/bin/sleep", "3650d"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we use mcr.microsoft.com/oss/kubernetes/pause:3.6
here too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will need to check, let me try to use the image and see if that works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to use the image but it fails with the error of bash not in PATH.
"bash": executable file not found in $PATH:
echo "trying to get the cilium_endpoints" | ||
kubectl exec -i "$cilium_agent" -n kube-system -- bash -c "cilium endpoint list -o json" > cilium_endpoints.json | ||
sleep 10 | ||
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what timeout is set on the pipeline? If there's a persistent error, this will loop indefinitely, but I'd expect GH actions eventually kills the process?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default timeout is 60 mins.
c545c83
to
03608f5
Compare
03608f5
to
8c61539
Compare
ci:[CNI] Load testing for cilium cni
ci:[CNI] Load testing for cilium cni
Reason for Change:
Add the load testing for cilium cni with aks cluster.
There are couple of scripts that does the testing.
Requirements:
Notes: