If you need to share a namespace with resources which are managed by other tools or indeed other krane deployments, you can supply the -selector option, such that only resources with labels matching the selector are considered for pruning. If you need to, you may specify -no-prune to disable all pruning behaviour, but this is not recommended. Sharing a namespaceīy default, krane will prune any resources in the target namespace which have the /last-applied-configuration annotation and are not a result of the current deployment process, on the assumption that there is a one-to-one relationship between application deployment and namespace, and that a deployment provisions all relevant resources in the namespace. Although we will fix any reported leak vectors with urgency, we cannot guarantee that sensitive information will never be logged. NOTICE: Deploy Secret resources at your own risk. -verbose-log-prefix: Add to the log prefix.-protected-namespaces=default kube-system kube-public: Fail validation if a deploy is targeted at a protected namespace.-no-verify-result: Skip verification that workloads correctly deployed.This is useful if you only want to deploy a subset of resources within a given YAML file. The deploy will not fail if not all resources match the labels. -selector-as-filter: Instructs krane to only deploy resources that are filtered by the specified labels in -selector.If you use this option, all resource templates must specify matching labels.
0 Comments
Leave a Reply. |