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

The WildFly ready check always fails when the container name is different with the project name #61

Open
jimma opened this issue May 23, 2023 · 0 comments

Comments

@jimma
Copy link

jimma commented May 23, 2023

The TestHelper#waitUntilWildFlyIsReady() always fails for the following deployment. This line checks the WildFly container log with some fixed container name :

String log = k8sClient.pods().withName(podName).inContainer(containerName).getLog();
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app.kubernetes.io/name: k8s-tests
  name: k8s-tests
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: k8s-tests
  template:
    metadata:
      labels:
        app.kubernetes.io/name: k8s-tests
    spec:
      containers:
        - name: wildflycontainer
          image: localhost:5000/k8s-tests:latest
          imagePullPolicy: Always
          ports:
            - containerPort: 9990
              name: admin
              protocol: TCP
            - containerPort: 8080
              name: http
              protocol: TCP

We can improve this by checking the WFLY readiness json response.

@jimma jimma changed the title The WildFly ready check always fails when the container The WildFly ready check always fails when the container name is different with the project name May 23, 2023
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

No branches or pull requests

1 participant