Open intrusus-dev opened 11 months ago
Thank you so much @intrusus-dev for the detailed information and solution. Would you like to make a PR for this?
Hi @intrusus-dev / @madhuakula I've created a PR for this.
Thanks @za !
Hi @intrusus-dev can you double check, it seems the issue has been solved without any changes on current main branch.
➜ kubernetes-goat git:(master) kgp
NAME READY STATUS RESTARTS AGE
batch-check-job-p4qhp 1/1 Running 0 4m13s
build-code-deployment-6ff7b98f7c-r4jgn 1/1 Running 0 4m12s
health-check-deployment-7f4fc7c947-6zk75 1/1 Running 0 4m11s
hidden-in-layers-nd6gn 1/1 Running 0 4m5s
internal-proxy-deployment-646b4cfcd7-gwlsq 2/2 Running 0 4m8s
kubernetes-goat-home-deployment-7f8486f6c7-q5jfw 1/1 Running 0 4m8s
metadata-db-7fbf595cc5-fpctd 1/1 Running 0 4m14s
poor-registry-deployment-877b55d89-hwh28 1/1 Running 0 4m7s
system-monitor-deployment-5466d8b787-tsv4f 1/1 Running 0 4m6s
I am running on AKS with Kubernetes version 1.28.9
Environment:
Platform: Azure AKS Affected Scenario: scenarios/health-check/deployment.yaml Kubernetes Goat Version: v2.2.0
Issue Description:
During the deployment of the Kubernetes Goat's "health-check" scenario on Azure AKS, I encountered a volume mount issue that prevented the pod from transitioning out of the "ContainerCreating" state. This issue appears to be specific to the Azure AKS platform.
Symptoms:
The "health-check" pod remained stuck in the "ContainerCreating" state. Logs showed errors related to mounting volumes, specifically the docker-sock-volume.
Troubleshooting:
hostPath
configuration in deployment.yaml.Resolution:
The issue was due to an incorrect type used for the docker-sock-volume
hostPath
. I updated the type toDirectoryOrCreate
, which resolved the volume mount problem.Steps to Reproduce:
kubectl get pods
Expected Behavior:
The "health-check" pod should transition from the "ContainerCreating" state to the "Running" state without any volume mount issues.
Recommendation:
Developers are advised to use the corrected type for the docker-sock-volume hostPath in the deployment.yaml file to ensure successful deployment on Azure AKS. To ensure compatibility, it's recommended to test the deployment specifically on Azure AKS, as this issue might not surface on other platforms.