Help me diagnose common issues with kn doctor

[scothis]

Like any distributed system, a Knative install includes a lot of moving parts. An error in any one of them can impact the behavior of the system. It would be nice to have a tool that can audit a cluster and check for common configuration issues.

Simple things to check:

• is knative serving installed
  • are the controller, webhook, activator and autoscaler ready
  • does the knative-ingressgateway service have an external ip (assuming it's a load balancer)
    • does the cluster's dns name resolve to that external ip
• is knative build installed
  • are the controller and webhook ready
• is knative eventing installed
  • are the controller and webhook ready
  • is the default channel provisioner installed
• is Istio installed
  • are the Istio deployments ready

A first pass can be fairly trivial so long as there is the ability to add in more advanced checks in the future.

[sixolet]

This sounds much more like an operator tool, rather than a developer tool, though a valuable one. It would depend on the knative implementation, not the knative API spec. Let's put it on the list that a parallel operator tools project should handle?

…

On Jan 10, 2019, at 8:33 AM, Scott Andrews ***@***.***> wrote: Like any distributed system, a Knative install includes a lot of moving parts. An error in any one of them can impact the behavior of the system. It would be nice to have a tool that can audit a cluster and check for common configuration issues. Simple things to check: is knative serving installed are the controller, webhook, activator and autoscaler ready does the knative-ingressgateway service have an external ip (assuming it's a load balancer) does the cluster's dns name resolve to that external ip is knative build installed are the controller and webhook ready is knative eventing installed are the controller and webhook ready is the default channel provisioner installed is Istio installed are the Istio deployments ready A first pass can be fairly trivial so long as there is the ability to add in more advanced checks in the future. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[vdemeester]

It could also pop up in a version or info command on the cli

[cppforlife]

+1 on separate tool for this kind of functionality as it seems to be more installation specific; however, i could see a similar command for a developer to diagnose problems with tree of resources that they deal with: service/builds/etc.

[maximilien]

Perfect as a plugin, once we figure that story out :)

[rhuss]

Agreed, especially as this kind of functionality touches the implementation of Knative, which could be different (like Kubernetes or Appengine)

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.