-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
After upgrade / installation of Kong Mesh 2.1 Prometheus server did not start due to missing / broken PVC on EKS #1232
Comments
@bartsmykla here |
Resolution was to install the CSI driver on EKS: https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi.html |
|
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
Couldn't find a PR for this, still relevant. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. |
What happened?
I have upgraded my whole cluster to 2.1 including fresh reinstall of observability by applying
No pods were created and after some search it turned out the EKS cluster was missing a role as described at https://docs.aws.amazon.com/eks/latest/userguide/managing-ebs-csi.html
The text was updated successfully, but these errors were encountered: