Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes Services Feedback #6

Open
dplain90 opened this issue Jul 6, 2019 · 4 comments
Open

Kubernetes Services Feedback #6

dplain90 opened this issue Jul 6, 2019 · 4 comments

Comments

@dplain90
Copy link

dplain90 commented Jul 6, 2019

Now that our pod is labelled more sensibly, we can configure a service to route traffic to it. The simplest way to expose a service is via ClusterIP — in a ClusterIP service, calls to the-service-name inside of the Kubernetes cluster will resolve to that ClusterIP.^[1] The service manifest will look like this:

^^ this doesn't read write grammatically and I had a hard time understanding.

I think one thing to change is that from my understanding the-service-name is just a filler word to describe the name of the service you are using it on. I think because most of the time in the lessons, you are using code text format highlighting to describe commands or names of things in the repo, it made me think you were describing a file or actual service instead of just a way to describe the context

@dplain90
Copy link
Author

dplain90 commented Jul 6, 2019

Yea I think it would help if you maybe stick to a certain pattern with the formatting.

Like make keywords bold and some secondary color or something. Then keep Comands/File stuff as code formatting

@dplain90 dplain90 changed the title Confusing Kubernetes Services Paragraph Kubernetes Services Feedback Jul 6, 2019
@dplain90
Copy link
Author

dplain90 commented Jul 6, 2019

This one is the most confusing I think so far. I think a diagram/picture would probably help describe whats happening a little better.

@dplain90
Copy link
Author

dplain90 commented Jul 6, 2019

So if you choose minikube, the load balancing thing is confusing af, since having is apparently normal, but with minikube it won't ever change for some reason.

However, when you do minikube service webapp it'll open chrome to the page and you can see the ip there.

@dplain90
Copy link
Author

dplain90 commented Jul 6, 2019

I liked the exercise for this one, but I kind of wish you didn't give me all the answers. I think it would have forced me to really internalize a little more if you were just like:

Create a service for topping-suggestion, it should be a ClusterIP service that accepts traffic on port 80 and forwards traffic to port 5678.

Based off the previous modules and what you describe above you should be able to figure all the rest out on your own, idk. Maybe thats just me but I think it would make it more challenging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant