mirrors/kyverno
1
0
Fork 0
mirror of https://github.com/kyverno/kyverno.git synced 2024-12-14 11:57:48 +00:00
Code Activity
kyverno/scripts
History
Shivkumar Dudhani 61b202c64a
420 init container (#501) 
* init container to cleanup stale webhook configurations if any.

* remove test code

* use internal pkg for os signals

* move webhook cleanup before http.server shutown.

* update make file and remove init

* update CI script
2019-11-18 11:41:37 -08:00
..
deploy-controller-debug.sh remove extra line for local debug 2019-07-03 14:11:18 -07:00
deploy-controller.sh remove unused yamls 2019-11-06 15:40:19 -08:00
generate-self-signed-cert-and-k8secrets-debug.sh - update install_debug.yaml - add debug log 2019-07-23 17:54:31 -07:00
generate-self-signed-cert-and-k8secrets.sh move client to pkg, helper script for self-signed certs & update documentation 2019-05-29 14:12:09 -07:00
generate-server-cert.sh Implemented test webhook, fixed script for certificate generation, fixed project dependencies 2019-02-21 18:13:21 +02:00
README.md 420 init container (#501) 2019-11-18 11:41:37 -08:00
update-codegen.sh update apiversion to v1 in code 2019-11-13 13:41:08 -08:00

README.md

Use these scripts to prepare the controller for work. All these scripts should be launched from the root folder of the project.

generate-server-cert.sh

Generates TLS certificate and key that used by webhook server. Example: scripts/generate-server-cert.sh --service=kyverno-svc --namespace=my_namespace --serverIp=192.168.10.117

  • --service identifies the service for in-cluster webhook server. Do not specify it if you plan to run webhook server outside the cluster, or cpecify 'localhost' if you want to run controller locally.
  • --namespace identifies the namespace for in-cluster webhook server. Do not specify it if you plan to run controller locally.
  • --serverIp is the IP of master node, it can be found in ~/.kube/config: clusters.cluster[0].server. You should explicitly specify it.

deploy-controller.sh

Prepares controller for free (local) or in-cluster use. Uses generate-server-cert.sh inside and has the same parameters with almost same meaning:

  • --service - the name of the service which will be created for the controller. Use 'localhost' value to deploy controller locally. The default is 'kube-policu-svc'
  • --namespace - the target namespace to deploy the controller. Do not specify it if you want to depoloy controller locally.
  • --serverIp means the same as for generate-server-cert.sh Examples: scripts/deploy-controller.sh --service=my-kyverno --namespace=my_namespace --serverIp=192.168.10.117 - deploy controller to the cluster with master node '192.168.10.117' to the namespace 'my_namespace' as a service 'my-kyverno' scripts/deploy-controller.sh --service=localhost --serverIp=192.168.10.117 - deploy controller locally for usage in cluster with master node at '192.168.10.117'

update-codegen.sh

Generates additional code for controller object. You should resolve all dependencies before using it, see main Readme for details.