-
Notifications
You must be signed in to change notification settings - Fork 6
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
Created Cilium Network Policy and Cilium Cluster Wide Network Policy Test #456
base: main
Are you sure you want to change the base?
Conversation
@microsoft-github-policy-service agree company="Microsoft" |
11ad9ee
to
354c931
Compare
- added CNP and CCNP template files - made changes to slo.py to include necessary variables - additions to load config and reconcile objects to include ccnp and cnp variables - added nginx deployment based on conditionals - created ccnp-cnp feature pipeline yaml - added necessary variables in existing slo steps
354c931
to
6162115
Compare
I created a Cilium Network Policy and Cilium Cluster Wide Network Policy pipeline that will deploy a set number of CCNPS and CNPS that match to nginx pods that allow traffic everywhere. It will also scale to a certain number of nodes and scale to a set number of nginx pods that will deploy and send dns requests to ipv4.bing.com or ipv6.bing.com based on user input. This test is created based on the existing service churn pipeline framework.
I created this test to be able to find the cilium cpu, memory, and apiserver usage through testing a 1000 node cilium cluster with endpoints as well as a 3000 node cilium cluster with CES enabled. This is for the upcoming official release of the cnp/ccnp feature.
Here is the link to my pipeline: https://dev.azure.com/akstelescope/telescope/_build?definitionId=37 and here is a link to a successful run: https://dev.azure.com/akstelescope/telescope/_build/results?buildId=8257&view=results
Since I made changes to files that the other pipelines use, I ran Service & Cluster Churn to ensure they were working as intended:
Service Churn Run: https://dev.azure.com/akstelescope/telescope/_build/results?buildId=8259&view=results
Service Churn Run with 1 repeat: https://dev.azure.com/akstelescope/telescope/_build/results?buildId=8196&view=results
Cluster Churn Run: https://dev.azure.com/akstelescope/telescope/_build/results?buildId=8272&view=results