Closed kkaempf closed 2 years ago
When I update the pod-privileged policy (because of kubewarden/kubewarden.io#26), helm just reports
pod-privileged
helm
clusteradmissionpolicy.policies.kubewarden.io/privileged-pods configured
So I looked at the policy-server logs (using k9s) to get some more information but it only shows
policy-server
Sep 17 08:56:33.432 INFO policy_server: policies download download_dir="/tmp/" policies_count=1 status="init" pulling policy... Sep 17 08:56:35.216 INFO policy_server: policies download status="done" Sep 17 08:56:35.216 INFO policy_server: kubernetes poller bootstrap status="init" Sep 17 08:56:35.216 INFO policy_server: kubernetes poller bootstrap status="done" Sep 17 08:56:35.216 INFO policy_server: worker pool bootstrap status="init" Sep 17 08:56:35.216 INFO policy_server::kube_poller: spawning cluster context refresh loop Sep 17 08:56:35.229 INFO policy_server::worker_pool: spawning worker spawned=2 total=2 Sep 17 08:56:35.230 INFO policy_server::worker_pool: spawning worker spawned=1 total=2 Sep 17 08:56:35.328 INFO policy_server: worker pool bootstrap status="done" Sep 17 08:56:35.333 INFO policy_server::server: started HTTPS server address="0.0.0.0:8443"
which doesn't tell me anything about
While the current log is helpful for developers, it doesn't contain information relevant for operators.
Related PR's:
When I update the
pod-privileged
policy (because of kubewarden/kubewarden.io#26),helm
just reportsSo I looked at the
policy-server
logs (using k9s) to get some more information but it only showswhich doesn't tell me anything about
While the current log is helpful for developers, it doesn't contain information relevant for operators.