I’ve been reaching out about several labs due to recurring issues. Quite often, I don’t receive any response when using the “report issue” button.
At the moment, I’m working through the Flux course. Lab 1 runs into performance problems once everything is installed, and Lab 3 doesn’t start at all. I’ve already provided feedback through the reporting option but haven’t received any reply.
I’ve experienced similar issues in other courses as well.
I’d like to emphasize that KodeKloud offers very good courses overall, and the labs are a major advantage compared to other providers. Since the labs are one of the main reasons for choosing KodeKloud, I personally believe it’s important that they work reliably.
I’m not sure exactly who responds to things you report through that mechanism, TBH. Reporting it here, though, one of the support engineers can create a report in our main system, which will get a response. Sorry for the delay in getting this dealt with, however.
Some of the labs seem to be working now, here’s some feedback:
LAB 1
I think it was this lab, where I was asked to create a source with timeout 10s but the validation was looking for interval 10s (otherwise it was lab 3)
LAB 3
works without any issues
LAB 4 - Deploy Application Manifest from a S3 Repo
The CA of the gitea instance isn’t imported, so you have to import the caFile, it’s not a task, and I think it wasn’t part of the labs before (I solved lab 2 a week ago, so I am not sure about it anymore)
UPDATE: the ca seems to be present on the system and is mentioned in the command in “click to expand”, so mentioning the file in the requirements, might already be the solution
LAB 5
Task 5 doesn’t mention the name of the resource to be created
caFile not set, same as in LAB 4
LAB 6 & 7
still not loading, I assume fixing the labs is still ongoing
Task 9, it’s not intuitiv were to store the encrypted secret especially as it’s required to override the input file
Task 12, the database-demo-kustomize-git-bb-app.yml isn’t available, you can solve the task by checking the solution and creating the file there with the solution.
Well, I first created the secret in the git repo, so it could be used again rather than replacing same file.
Lab 10:
it would be nice if the ca-file was mentioned in the description and not only in the (hidden) template
on task 10 it would be nice to mention the url again, it was used in earlier commands, but as all other parameters are mentioned, it makes sense
in general the lab works smoothly
Lab 11:
same for the ca-file. For those, who type the command directly instead of using the template, it would help a lot
on task 5 the file path and the note are quite confusing no idea, why the task doesn’t just state /root/pod-monitor-and-grafana-dashboard.yml or as in the the ~/pod-monitor-and-grafana-dashboard.yml
in general the lab was do-able, but neither prometheus nor grafana looked healthy, so seeing anything there wasn’t possible and the bootstrap command wasn’t finished when I finished the lab, so there seem to be some performance issues.
no idea, why the task doesn’t just state /root/pod-monitor-and-grafana-dashboard.yml or as in the the ~/pod-monitor-and-grafana-dashboard.yml