Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add analyzers to support bundle. Useful for auto-solving common problems #8865

Closed
3 tasks
Tracked by #8840 ...
mrsimonemms opened this issue Mar 17, 2022 · 1 comment
Closed
3 tasks
Tracked by #8840 ...
Labels
team: delivery Issue belongs to the self-hosted team

Comments

@mrsimonemms
Copy link
Contributor

mrsimonemms commented Mar 17, 2022

Analyzers are an important part of the Replicated support bundle

Establish a list of common problems with a Gitpod installation and ways of checking automatically. The preflights will likely be a good part of that.

A discussion with Barry @ Replicated as to his recommendations/what other Replicated user do may be a good initial step

Suggestions

  • Most common (current) issue is Check EKS guide for registry validity #8855. Suggest writing a collector to look for relevant log in pod and then create analyzer to suggest possible resolutions. Typically, these have x509 in the errors
  • Had someone recently who had problems due to only setting up DNS/certs for $DOMAIN - add DNS check for $DOMAIN, *.$DOMAIN and *.ws.$DOMAIN
  • Add warning for self-signed certs
@mrsimonemms
Copy link
Contributor Author

As of today, I don't think we need to do anything with this. The requirements for this should largely be driven by the Support Team as this is designed to automate the common questions.

The preflight checks have a lot of analyzers in and (seem) to catch most of the common questions before deployment.

I will close this, but inform the support team that we can add in additional tests as they require

/cc @mrzarquon

@mrsimonemms mrsimonemms closed this as not planned Won't fix, can't repro, duplicate, stale Jul 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team: delivery Issue belongs to the self-hosted team
Projects
None yet
Development

No branches or pull requests

1 participant