1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2024-12-14 11:57:48 +00:00
kyverno/test
2019-05-21 18:38:52 -07:00
..
ConfigMap update example due to crd name changed 2019-05-21 18:38:52 -07:00
ConfigMapGenerator-SecretGenerator update example due to crd name changed 2019-05-21 18:38:52 -07:00
CronJob update example due to crd name changed 2019-05-21 18:38:52 -07:00
DaemonSet update example due to crd name changed 2019-05-21 18:38:52 -07:00
Deployment update example due to crd name changed 2019-05-21 18:38:52 -07:00
Endpoint update example due to crd name changed 2019-05-21 18:38:52 -07:00
HorizontalPodAutoscaler update example due to crd name changed 2019-05-21 18:38:52 -07:00
Ingress updated policies 2019-05-21 17:56:59 +03:00
Job new policy structure 2019-05-21 17:54:55 +03:00
LimitRange new policy structure 2019-05-21 17:54:55 +03:00
Namespace new policy structure 2019-05-21 17:54:55 +03:00
NetworkPolicy updated policies 2019-05-21 17:56:59 +03:00
PersistentVolumeClaim new policy structure 2019-05-21 17:54:55 +03:00
PodDisruptionBudget new policy structure 2019-05-21 17:54:55 +03:00
PodTemplate new policy structure 2019-05-21 17:54:55 +03:00
ResourceQuota updated policies 2019-05-21 17:56:59 +03:00
Secret updated policies 2019-05-21 17:56:59 +03:00
Service updated policies 2019-05-21 17:56:59 +03:00
StatefulSet new policy structure 2019-05-21 17:54:55 +03:00
README.md - Change kube-policy to kyverno in install.yaml - Install in namespace kyverno 2019-05-21 18:36:24 -07:00

Examples

Examples of policies and resources with which you can play to see the kyverno in action. There are definitions for each supported resource type and an example policy for the corresponding resource.

How to play

First of all, build and install the policy controller: see README file in the project's root. Each folder contains a pair of files, one of which is the definition of the resource, and the second is the definition of the policy for this resource. Let's look at an example of the endpoints mutation. Endpoints are listed in file examples/Endpoints/endpoints.yaml:

kind: Endpoints
metadata:
  name: test-endpoint
  labels:
    label : test
subsets:
- addresses:
  - ip: 192.168.10.171
  ports:
  - name: secure-connection
    port: 443
    protocol: TCP

Create this resource:

> kubectl create -f examples/Endpoints/endpoints.yaml
endpoints/test-endpoint created
> kubectl get -f examples/Endpoints/endpoints.yaml
NAME            ENDPOINTS            AGE
test-endpoint   192.168.10.171:443   6s

We just created an endpoints resource and made sure that it was created without changes. Let's remove it now and try to create it again, but with an active policy for endpoints resources.

> kubectl delete -f test/endpoints.yaml
endpoints "test-endpoint" deleted

We have this a policy for enpoints (examples/Endpoints/policy-endpoint.yaml):

apiVersion : kubepolicy.nirmata.io/v1alpha1
kind : Policy
metadata :
  name : policy-endpoints
spec :
  rules:
    - name:
      resource:
        kind : Endpoints
        selector:
          matchLabels:
            label : test
      mutate:
        patches:
          - path : "/subsets/0/ports/0/port"
            op : replace
            value: 9663
          - path : "/subsets/0"
            op: add
            value:
              addresses:
              - ip: "192.168.10.171"
              ports:
              - name: load-balancer-connection
                port: 80
                protocol: UDP

This policy does 2 patches:

  • replaces the first port of the first connection to 6443
  • adds new endpoint with IP 192.168.10.171 and port 80 (UDP)

Let's apply this policy and create the endpoints again to see the changes:

> kubectl create -f examples/Endpoints/policy-endpoints.yaml
policy.policy.nirmata.io/policy-endpoints created
> kubectl create -f examples/Endpoints/endpoints.yaml
endpoints/test-endpoint created
> kubectl get -f examples/Endpoints/endpoints.yaml
NAME            ENDPOINTS                               AGE
test-endpoint   192.168.10.171:80,192.168.10.171:9663   30s

As you can see, the endpoints resource was created with changes: a new port 80 was added, and port 443 was changed to 6443.

Enjoy :)