Fix issue with LAMP Environment in Kubernetes

KodeKloud Engineer
#26

thanks @rahul456 that is would be task for 15th Nov. yet to get the lost task for other days please?

#27

@rahul456 apologies for nagging on this issue many times, but the task is still pending, I think that is preventing us from getting new tasks. so if you can remove it from our bucket until it get fixed. or should we proceed with the task and you guys can mark it as success?

#28

I saw 3-4 types of questions related to LAMP stack. All are failing :frowning: I faced another one today and this task also had a similar problem :frowning:

@Ayman Will, you check and mark all my lamp stack tasks to available state?

#29

@nashwan, that issue task was marked as expired and new task was also assgined to you 3 days before.

#30

@rahul456 actually you marked a review reward as expired.plus you shouldnt mark it as expired instead remove it from my bucket because that will show another incomplete task in my bucket which is not fair. Would be great if you remove it and please revert the reward point to which you marked it as expired

Also because of this issue i only got two task from.10 to 18th nov. This is really not fair. But if you think i only deserver to be treated this way. I cant do anything but will indeed be disappointed.
.

#31

@nashwan, marked success for you.

#32

Thanks @rahul456 but i can still see it as pending. You may have recorrected the review reward points which i got it for reviwing others task.but not mark this task as success. Its still showing pending.

#33

@nashwan, please check once, if that task success ?

#34

@rahul456, Can I get an answer on my request too? Did you checked my task ? Can I get an input too?

#35

@kleansoul, can you please share your KKE user details ?

#37

@kleansoul, this is marked success for you.

1 Like
#38

@rahul456 Thanks for your reply.

#39

@rahul456 yes its marked as success, but I donot know why this task is marked as expired?

Reviewed for MS : Fix issue with LAMP Environment in Kubernetes Nov 13, 2020 12:32:00 AM
200
Expired

( can you please re-correct his as well)

#40

@rahul456 Will you please review and assing back my tasks too? I faced lamp stack tasks more than 6 times :slight_smile:

#41

@rahul456 I was able to load the WordPress but the validation said there is something wrong with environment variables. I have also submitted the task for review

Wordpress website

image
image1390×749 66.2 KB

image
image1393×749 103 KB

image
image1394×751 80.5 KB

image
image1390×747 48 KB

image
image1390×746 42.8 KB

mysql container environment variables in a deployment:

image
image334×630 6.59 KB

Regards,
Salim

#42

@rahul456 @Inderpreet can you please check this for me?thanks.

#43

@Salim Maybe this is the similar issue mentioned in this thread ?

#44

Thanks for the input, I managed to resolve the issue @Inderpreet :slightly_smiling_face:

1 Like
#45

Looks like Kodekloud still give this lab. Got this Aug 2023.
Lab is extremely buggy, did the correct steps multiple times, even followed the suggestions in this thread but lab kept failing. Was about to skip it because I already wasted a day working on it. Left it and returned after an hour, did the same steps again, and voila, it worked. Somehow there is no way to visually verify if the app was deployed successfully - meaning the Wordpress site doesn’t appear. It just showed “Connected successfully”. I added all my notes here for anyone who’s interested to know:

#47

kubectl get deploy
kubectl describe deploy lamp-wp

#will see portno is wrong
kubectl get service

#change port no
kubectl edit service lamp-service

change node port to 30008

kubectl get configmap
kubectl describe configmap eg.php-config

kubectl get deploy
kubectl get pods
kubectl describe pods

kubectl get pods
kubectl exec -it -c httpd-php-container – sh
ls
cd app/
ls
cat index.php

copy index.php
exit
vi index.php
CHANGE HOST-MYSQL to MYSQL_HOST
CHANGE MYSQL_PASSWORDS to MYSQL_PASSWORD

kubectl create configmap --help
kubectl create configmap index --from-file=index.php

kubectl get configmap
#MYSQLHost was updated
kubectl describe configmap index
kubectl edit deployment lamp-wp

below SubPath

  • mountPath: /app/index.php
    name: index
    subPath: index.php

below name: php-config-volume

  • configMap:
    defaultMode: 420
    name: index
    name: index

kubectl get Pods

#mount path was changed after editing
kubectl describe pod

#validate
kubectl exec -it -c httpd-php-container – sh
ls
cd app/
ls
cat index.php

1 Like