-
Notifications
You must be signed in to change notification settings - Fork 7
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
Conversation
@microsoft-github-policy-service agree company="Microsoft" |
11ad9ee
to
354c931
Compare
354c931
to
6162115
Compare
c6a2b00
to
43d8920
Compare
the purpose of test is still trying to exercise control plane with crds reconcile, that's why the actual polices are empty, then why do we need nginx and ping traffic? |
43d8920
to
960f958
Compare
8458657
to
d1e8fe3
Compare
Updated Changes:
|
- 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
- added ingress and egress rules to ccnp & cnp template to reflect customer usage for control plane resource usage testing
f1a7891
to
c09f823
Compare
I responded to the question in chat. There should not be nginx and pod traffic, I made changes to remove nginx pods, removed ping traffic, and I am utilizing container image that was already present. I also added rules to the cnp and ccnp template to reflect customer usage to be able to test control plane resource usage consumption. |
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.
thanks Karina!
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 pods. It will also scale to a certain number of nodes and scale to a set number of pods. The policies have egress and ingress rules to reflect customer usage and to be able to test control plane resource usage consumption. 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=9548&view=results
Since I made changes to files that the other pipelines use, I'm running Service & Cluster Churn:
Regular Pipelines: