Resolve "Create networkpolicies for gitlab-runner"

Create networkpolicies for gitlab-runner
also add istio integration with PeerAuthentication and NetworkPolicy

related BB MR big-bang/bigbang!2581 (merged)

Closes #55 (closed)

changed milestone to %2.0.0

added gitlabRunner statusdoing teambigbang labels

assigned to @kevin.wilder

assigned to @jason.flowers

added 1 commit

• e63fe5e3 - add networkpolicies

Compare with previous version

added 1 commit

• cd64c126 - captial N

Compare with previous version

added 1 commit

• 4b5fe541 - add controlPlaneCidr

Compare with previous version

added 1 commit

• a7866ec6 - access kube-api

Compare with previous version

added 1 commit

• 74f86663 - ns not equal to gitlab

Compare with previous version

added 1 commit

• 9eb08007 - update readme

Compare with previous version

added 1 commit

• 844cf266 - add and

Compare with previous version

I tested BB 1.x and BB 2.0

marked this merge request as ready

added statusreview label and removed statusdoing label

requested review from @micah.nagel

requested review from @ryan.j.garcia

Do we want to consider adding something like the wrapper's extra network policies via values? https://repo1.dso.mil/big-bang/product/packages/wrapper/-/blob/main/chart/templates/network/networkpolicy-additional.yaml

I think this has a great usecase for runner since people may want specific jobs to specific ingress/egress. Thinking of our dogfood cluster we could create a policy via values to allow sonarqube egress. Totally fine to say no and make this a future enhancement - although I'd suspect our default policies will cause most people issues if they are running any jobs that reach outside of the cluster.

requested review from @LynnStill