Using Multi-Node Clusters

[davidegallo]

What Happened?

Good example about PODS running in different nodes, anyway I think that the deployment .yaml file needs more explanation about affinity and the fact that the Target port = http shall be the same in PODS AND Service .yaml files ...

Attach the log file

Operating System

Other

Driver

Docker

[T-Lakshmi]

@davidegallo,
Can you please share more details about the issue/suggestion you are talking about.
Please provide url too you are talking about.

[T-Lakshmi]

/triage needs-information

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[Ritikaa96]

Related page: https://minikube.sigs.k8s.io/docs/tutorials/multi_node/
/kind feature
/kind docs

[k8s-ci-robot]

@Ritikaa96: The label(s) kind/docs cannot be applied, because the repository doesn't have them.

In response to this:

Related page: https://minikube.sigs.k8s.io/docs/tutorials/multi_node/
/kind feature
/kind docs

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-sigs/prow repository.

[Ritikaa96]

@davidegallo i see what you are saying ,

• this line below is sudden and unexplained after the services url is pinged

Multiple nodes!

• regarding deployment file , i think there is no explanation needed . as this is a tutorial and the description is written as referenced deployment files

[Ritikaa96]

What we can write in improvement under this section is:

Let’s hit the URL a few times and see what comes back
curl http://192.168.49.2:31000
Hello from hello-695c67cf9c-frcvw (10.244.0.3)

curl http://192.168.49.2:31000
Hello from hello-695c67cf9c-bzrzk (10.244.1.2)

curl http://192.168.49.2:31000
Hello from hello-695c67cf9c-bzrzk (10.244.1.2)

curl http://192.168.49.2:31000
Hello from hello-695c67cf9c-frcvw (10.244.0.3)
Multiple nodes!
When we hit the URL few times , we see the pods from all nodes are pinged.

[Ritikaa96]

/kind documentation

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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-sigs/prow repository.