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

Kubernetes wildfly pod deployment fails to start #76493

Closed
1090223 opened this Issue Apr 12, 2019 · 6 comments

Comments

Projects
None yet
3 participants
@1090223
Copy link

1090223 commented Apr 12, 2019

I have a kubernetes wildflypod and kubernetes postgres pod. I have specified env variables so that they can talk to each other but this is not working. But when I am linking these containers in docker it is working fine. What could be possibly wrong?

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

k8s-ci-robot commented Apr 12, 2019

@1090223: There are no sig labels on this issue. Please add a sig label by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@neolit123

This comment has been minimized.

Copy link
Member

neolit123 commented Apr 13, 2019

/triage needs-information

please provide more details about your setup OS, kubernetes version, cluster setup, other conditions.
also it might be a better idea to ask on stackoverflow or reddit.

@1090223

This comment has been minimized.

Copy link
Author

1090223 commented Apr 16, 2019

OS is CentOS 7.5, Kubernetes major version:1 and minor:12 , cluster is setup on CentOS 7.5 servers. One is master and other is worker node. Please tell a way by which i can troubleshoot this issue.

@1090223

This comment has been minimized.

Copy link
Author

1090223 commented Apr 18, 2019

@neolit123 Any suggestion from your side?

@neolit123

This comment has been minimized.

Copy link
Member

neolit123 commented Apr 18, 2019

i think you will get better feedback in community forums like stackoverflow or reddit.
i haven't seen much talks about wildfly in k8s, which leads me to believe that the k8s maintainers and people who monitor the issue tracker cannot answer your question.

i'm going to have to close this ticket, but feel free to try the above recommendation - e.g.:
https://stackoverflow.com/search?q=%5Bkubernetes%5D+wildfly

thanks
/close

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

k8s-ci-robot commented Apr 18, 2019

@neolit123: Closing this issue.

In response to this:

i think you will get better feedback in community forums like stackoverflow or reddit.
i haven't seen much talks about wildfly in k8s, which leads me to believe that the k8s maintainers and people who monitor the issue tracker cannot answer your question.

i'm going to have to close this ticket, but feel free to try the above recommendation - e.g.:
https://stackoverflow.com/search?q=%5Bkubernetes%5D+wildfly

thanks
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.