Skip to content

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

@jimma

Description

@jimma

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions