Error vote results

#1

Hi,
I am very very new to Kubernetes and thought I was getting the hang of it after going through the kodecloud crash course until running into the final lab which is “Deploying voting app on Kubernetes”. I am stuck from out the gate. I have found several similar manifests online which I have tried to augment to the results required but am still in the red.

This is what is required for the Vote Service:
Create a new service: name = vote-service
port = ‘5000’
targetPort = ‘80’
nodePort= ‘31000’

This is my code which does get created without error but still does not pass the check:
apiVersion: v1
kind: Service
metadata:
name: vote-service
labels:
name: vote-service
app: demo-vote-app
spec:
type: NodePort
ports:
- port: 5000
targetPort: 80
nodePort: 31000
selector:
name: vote-app-pod
app: demo-vote-app
Not even one item passed.

#2

Hi @Browmaul

It would have helped us if you could share the YAML in a code block. You can do this by putting the YAML in three backticks or by using the </> button available in the editor ribbon at the top.

Also, can you share the link to the KodeKloud lab you are trying this on?

#3

The correct YAML to deploy voting app and not have it crash is here.

But as Santosh has asked, please share the lab link

#4

Thank you both and I will be more detailed going forward. I am still getting used to this and such forums. Very very helpful solve which taught me so very much. I will be leaning on this forum and quite a bit until getting a hang of this subject matter which seems so insane at the moment.

Kodekloud crash course final Vote Deploy lab.

#5

Using the yaml file from the github link did not resolve the issue for some reason. Is is possible anyone can tell me why?

#6

I see what the issue is. The resource names for this task do not align with the YAML files. I will raise a ticket to have them aligned

#7

Thanks a lot.
While I’m sure I have tons to work on as far as my basic understanding, I’m glad that I wasn’t totally at fault. Now I know to paste all related material in the chat for a faster resolution.

Have a great weekend!

#8

Hello sir,
Did you get to open a ticket and do you know if it has yet been resolved?
Thanks again for your assistance.

#9

Hello @Browmaul

The current state of the ticket is “To Close” which means it’s ready to be tested by users. Please try it again and let me know.
It should now be aligned with the YAML that is in the repo, but be sure to deploy everything in the correct namespace as directed by the question.