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

Bug: resource tree bad gateway #4614

Closed
2 tasks done
iamayushm opened this issue Jan 31, 2024 · 0 comments · Fixed by #4613
Closed
2 tasks done

Bug: resource tree bad gateway #4614

iamayushm opened this issue Jan 31, 2024 · 0 comments · Fixed by #4613
Assignees
Labels
bug Something isn't working pager-duty Bugs / Issues found while on pager duty

Comments

@iamayushm
Copy link
Contributor

iamayushm commented Jan 31, 2024

📜 Description

it bugs out when some charts are deployed via gitOps.

👟 Reproduction steps

Deploy below manifest using generic helm chart. Resource tree api will give bad gateway.

apiVersion: v1
kind: Pod
spec:
containers:
- command:
- /bin/sh
- '-c'
- >-
apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install
--no-install-recommends --assume-yes postgresql-client
image: ubuntu
name: cnpg-testing
ports:
- containerPort: 80

👍 Expected behavior

Resource tree api should not throw bad gateway

👎 Actual Behavior

resource tree throws bad gateway

☸ Kubernetes version

EKS 1.23

Cloud provider

azure

🌍 Browser

Chrome

🧱 Your Environment

No response

✅ Proposed Solution

No response

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

AB#8308

@iamayushm iamayushm added the bug Something isn't working label Jan 31, 2024
@tayalrishabh96 tayalrishabh96 added the pager-duty Bugs / Issues found while on pager duty label Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working pager-duty Bugs / Issues found while on pager duty
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants