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

Update document for Azure LoadBalancer support. #4082

Merged
merged 4 commits into from
Jul 27, 2017

Conversation

karataliu
Copy link
Contributor

@karataliu karataliu commented Jun 14, 2017

Document update for following 2 PRs:


This change is Reviewable

Copy link
Contributor

@chenopis chenopis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One small nit. Docs LGTM otherwise.

@@ -429,10 +429,18 @@ with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not s
an ephemeral IP will be assigned to the loadBalancer. If the `loadBalancerIP` is specified, but the
cloud provider does not support the feature, the field will be ignored.

#### Internal load balancer on AWS
Special notes for Azure: To use user-specified public type `loadBalancerIP`, a static type
public IP address resource need to be created at first, and it should be in the same resource
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"need" -> "needs"

@karataliu
Copy link
Contributor Author

Thanks for comment. Update pushed.

@chenopis
Copy link
Contributor

ping @bprashanth

@@ -429,10 +429,18 @@ with the user-specified `loadBalancerIP`. If the `loadBalancerIP` field is not s
an ephemeral IP will be assigned to the loadBalancer. If the `loadBalancerIP` is specified, but the
cloud provider does not support the feature, the field will be ignored.

#### Internal load balancer on AWS
Special notes for Azure: To use user-specified public type `loadBalancerIP`, a static type
public IP address resource needs to be created at first, and it should be in the same resource
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

public IP address resource needs to be created first, and it should be in the same resource

@jdumars
Copy link
Member

jdumars commented Jul 12, 2017

Added one small suggestion. Otherwise LGTM.

@chenopis chenopis merged commit 2f50a22 into kubernetes:master Jul 27, 2017
chenopis added a commit that referenced this pull request Jul 28, 2017
…hub.io into netlify-move

* 'master' of https://github.com/kubernetes/kubernetes.github.io:
  Simplify sentence
  minor correction for datastore storage folder
  Fix spelling error (#4528)
  Updated Getting Started Guide for vSphere Cloud Provider
  In links to ref pages, use {{page.version}}.
  Update backlinks to client libraries page
  Translate getting-started-guides/centos/centos_manual_config.md into Chinese
  update version No. to para. (#4442)
  Change deprecated `kubectl update` to `replace` (#4307)
  Revert "add host paths to psp (#3971)"
  docs/concepts/policy/pod-security-policy.md: update link to example.
  change the limit to request
  concepts/storage: fix minor typo in volumes.md
  kubeadm: Make tabs with information how to install 3rd-party CNI network solutions
  Add docs for running cloud-controller-manager with persistent volume labeling
  Update document for Azure LoadBalancer support. (#4082)
  Add note about rkt under CRI to rktnetes page (#4470)
  Delete redundant "see" (#4466)
  Allow importing of manifest files with tutorial import script

# Conflicts:
#	docs/setup/independent/create-cluster-kubeadm.md
#	docs/tasks/administer-cluster/cpu-memory-limit.md
#	docs/tasks/configure-pod-container/security-context.md
jesscodez pushed a commit that referenced this pull request Sep 22, 2017
* Add doc for azure internal load balancer support.

* Add note for user-specified 'loadBalancerIP' support on Azure.

* Fix comment.

* Fix comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants