Problem
The Kubernetes scenario setup script runs during Docker image build, but kind clusters are ephemeral and don't persist in the built image.
Current Behavior
setup.sh is executed in the Dockerfile with RUN /home/devops/setup.sh
- This creates a kind cluster during image build
- When the container starts from this image, the kind cluster doesn't exist
Expected Behavior
- The kind cluster should be created when the container starts
- Users should see the cluster being created as part of the scenario initialization
Root Cause
In scenarios/kubernetes/keycloak-crashloop/Dockerfile:
# This runs at build time
RUN /home/devops/setup.sh
Solution
- Remove the
RUN /home/devops/setup.sh from Dockerfile
- Create an entrypoint script that runs setup.sh at container start
- Use
ENTRYPOINT or CMD to execute the setup when container starts
Impact
- Kubernetes scenarios appear broken as no cluster exists when users connect
- The "Creating kind cluster..." message never appears to users
Problem
The Kubernetes scenario setup script runs during Docker image build, but kind clusters are ephemeral and don't persist in the built image.
Current Behavior
setup.shis executed in the Dockerfile withRUN /home/devops/setup.shExpected Behavior
Root Cause
In
scenarios/kubernetes/keycloak-crashloop/Dockerfile:Solution
RUN /home/devops/setup.shfrom DockerfileENTRYPOINTorCMDto execute the setup when container startsImpact