-
Notifications
You must be signed in to change notification settings - Fork 149
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
IPv6 address support in node addresses #561
base: master
Are you sure you want to change the base?
Changes from 3 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -62,7 +62,7 @@ package-hosted directory like this: | |||||
|
||||||
```bash | ||||||
cd cloud-controller-manager/cmd/digitalocean-cloud-controller-manager | ||||||
REGION=fra1 DO_ACCESS_TOKEN=your_access_token go run main.go \ | ||||||
REGION=fra1 DO_ACCESS_TOKEN=your_access_token DO_IP_ADDR_FAMILIES=ipv4 go run main.go \ | ||||||
--kubeconfig <path to your kubeconfig file> \ | ||||||
--leader-elect=false --v=5 --cloud-provider=digitalocean | ||||||
``` | ||||||
|
@@ -79,6 +79,11 @@ You might also need to provide your DigitalOcean access token in | |||||
the cloud controller to start, but in that case, you will not be able to | ||||||
validate integration with DigitalOcean API. | ||||||
|
||||||
The `DO_IP_ADDR_FAMILIES` is used to configure the required IP familes and the | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Typo: families There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. fixed |
||||||
order in which address should be populated in nodes status. The accepted values | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. fixed |
||||||
are one of the `{"", "ipv4", "ipv6", "ipv4,ipv6", "ipv6,ipv4"}`.IPv4 is the | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why do we have curly braces here? It almost looks like JSON but we don't require JSON, do we? Can we rephrase this in a more user friendly manner, e.g., say There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. fixed |
||||||
default, if not set or empty. | ||||||
|
||||||
Please note that if you use a Kubernetes cluster created on DigitalOcean, there | ||||||
will be a cloud controller manager running in the cluster already, so your local | ||||||
one will compete for API access with it. | ||||||
|
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.
I'd omit the usage from this example since it's not strictly needed when running locally.
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.
Fixed