-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update accessing apps service doc #13806
Update accessing apps service doc #13806
Conversation
Hi @zhan9san. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Can one of the admins verify this patch? |
@@ -11,6 +11,8 @@ aliases: | |||
|
|||
There are two major categories of services in Kubernetes: | |||
|
|||
[publishing-services-service-types](https://kubernetes.io/docs/concepts/services-networking/service/#publishing-services-service-types) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this doesnt seem to be relevent,
it says
"
There are two major categories of services in Kubernetes:
[publishing-services-service-types]
"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @medyagh
I though it may help users to access the kubernetes service type here.
This line has been removed and the PR is rebased on master branch.
Could you kindly review it again?
a23d3ac
to
2b16bfd
Compare
I found the information contained in the updated docs very useful and would have appreciated it in the latest (online) version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just grammatical and capitalization changes, I'll be happy to merge once addressed
|
||
### Example of NodePort | ||
|
||
1. Create a kubernetes deployment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Create a kubernetes deployment | |
1. Create a Kubernetes deployment |
kubectl create deployment hello-minikube1 --image=k8s.gcr.io/echoserver:1.4 | ||
``` | ||
|
||
2. Create a kubernetes service type NodePort |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2. Create a kubernetes service type NodePort | |
2. Create a Kubernetes service type NodePort |
minikube service hello-minikube1 --url | ||
``` | ||
|
||
`minikube service hello-minikube1 --url` runs as a process, creating a [tunnel](https://en.wikipedia.org/wiki/Port_forwarding#Local_port_forwarding) to cluster. The command exposes the service directly to any program running on the host operating system. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
`minikube service hello-minikube1 --url` runs as a process, creating a [tunnel](https://en.wikipedia.org/wiki/Port_forwarding#Local_port_forwarding) to cluster. The command exposes the service directly to any program running on the host operating system. | |
`minikube service hello-minikube1 --url` runs as a process, creating a [tunnel](https://en.wikipedia.org/wiki/Port_forwarding#Local_port_forwarding) to the cluster. The command exposes the service directly to any program running on the host operating system. |
</pre> | ||
</details> | ||
|
||
check ssh tunnel in another terminal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
check ssh tunnel in another terminal | |
Check ssh tunnel in another terminal |
|
||
5. Try in your browser | ||
|
||
open in your browser (make sure there is no proxy set) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
open in your browser (make sure there is no proxy set) | |
Open in your browser (ensure there is no proxy set) |
http://REPLACE_WITH_EXTERNAL_IP:8080 | ||
``` | ||
|
||
Each service will get its own external ip. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Each service will get its own external ip. | |
Each service will get its own external IP. |
## Getting the NodePort using kubectl | ||
### Using `minikube service` with tunnel | ||
|
||
The network is limited if you are using a Docker driver on darwin, Windows or WSL, and the Node IP is not reachable directly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The network is limited if you are using a Docker driver on darwin, Windows or WSL, and the Node IP is not reachable directly. | |
The network is limited if using the Docker driver on Darwin, Windows, or WSL, and the Node IP is not reachable directly. |
|
||
#### Run tunnel in a separate terminal | ||
1. Run tunnel in a separate terminal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Run tunnel in a separate terminal | |
1. Run the tunnel in a separate terminal |
|
||
note that without minikube tunnel, kubernetes would be showing external IP as "pending". | ||
4. Check external IP |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
4. Check external IP | |
4. Check the external IP |
|
||
The network is limited if you are using a Docker driver on darwin, Windows or WSL, and the Node IP is not reachable directly. | ||
|
||
If minikube runs on Linux with Docker driver, no tunnel will be created. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If minikube runs on Linux with Docker driver, no tunnel will be created. | |
Running minikube on Linux with the Docker driver will result in no tunnel being created. |
Hi @spowelljr Thanks for your careful review. Could you help review it again? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thank you!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: spowelljr, zhan9san The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
fix #13788 #13747
Would you kindly review this doc update?