Skip to content
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

Open
svenwal opened this issue Feb 3, 2023 · 11 comments
Labels
kind/improvement Improvement on an existing feature triage/accepted The issue was reviewed and is complete enough to start working on it triage/stale Inactive for some time. It will be triaged again

Comments

@svenwal
Copy link
Contributor

svenwal commented Feb 3, 2023

What happened?

I have upgraded my whole cluster to 2.1 including fresh reinstall of observability by applying

kumactl install observability | kubectl delete -f -
kumactl install observability | kubectl apply -f -

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

@svenwal svenwal added kind/bug A bug triage/pending This issue will be looked at on the next triage meeting labels Feb 3, 2023
@svenwal
Copy link
Contributor Author

svenwal commented Feb 3, 2023

@bartsmykla here

@lahabana
Copy link
Contributor

lahabana commented Feb 3, 2023

Resolution was to install the CSI driver on EKS: https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi.html

@jakubdyszkiewicz jakubdyszkiewicz transferred this issue from kumahq/kuma Feb 6, 2023
@jakubdyszkiewicz
Copy link
Contributor

Triage: there is not much we can do in the code. Let's document it

@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it kind/improvement Improvement on an existing feature and removed triage/pending This issue will be looked at on the next triage meeting kind/bug A bug labels Feb 6, 2023
@github-actions
Copy link
Contributor

github-actions bot commented May 8, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label May 8, 2023
@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label May 8, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Aug 7, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Aug 7, 2023
@bartsmykla bartsmykla removed the triage/stale Inactive for some time. It will be triaged again label Aug 8, 2023
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Nov 7, 2023
Copy link
Contributor

github-actions bot commented Nov 7, 2023

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Nov 7, 2023
Copy link
Contributor

github-actions bot commented Feb 6, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Feb 6, 2024
@slonka slonka removed the triage/stale Inactive for some time. It will be triaged again label Feb 7, 2024
@slonka
Copy link
Contributor

slonka commented Feb 7, 2024

Couldn't find a PR for this, still relevant.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label May 8, 2024
Copy link
Contributor

github-actions bot commented May 8, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label May 20, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Aug 19, 2024
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Aug 19, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Nov 18, 2024
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
kind/improvement Improvement on an existing feature triage/accepted The issue was reviewed and is complete enough to start working on it triage/stale Inactive for some time. It will be triaged again
Projects
None yet
Development

No branches or pull requests

6 participants