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

ENDOC-600 correct logs text on Troubleshooting ECR #609

Merged
merged 4 commits into from
Oct 31, 2022
Merged

Conversation

jyunmitch
Copy link
Collaborator

No description provided.

### Solution
If your Entando cluster has more than one Entando App custom resource, find the component manager in question using the Entando App name and namespace where the app has been deployed. Assuming you have a single Entando App named `quickstart` and your cluster namespace is called `YOUR-NAMESPACE`,
If your Entando cluster has more than one Entando App custom resource, find the component manager in question using the EntandoApp name in the namespace where the app has been deployed. Assuming you have a single EntandoApp named `quickstart`,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is the first entando app not one word?

"find the component manager in question" is a little wordy and imprecise (the CM is not directly discussed here, nor is it under investigation or a source of controversy). find the applicable component manager? correct, appropriate, etc...

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this alerted me to the fact that the command below is not the right one. It actually should be the cm deployment. Reworded

Copy link
Contributor

@Lyd1aCla1r3 Lyd1aCla1r3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor clarifications

```
kubectl logs -f deployment/quickstart-server-deployment --namespace YOUR-NAMESPACE -c de-container
ent k logs -f YOUR-PODNAME-7f74757f97-xnlbn -n YOUR-NAMESPACE
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could add a note that the namespace (-n) is optional if ent has a profile configured.

@jyunmitch jyunmitch merged commit 104f6c1 into main Oct 31, 2022
@jyunmitch jyunmitch deleted the ENDOC-600 branch October 31, 2022 20:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants