Skip to content
This repository has been archived by the owner on Jul 30, 2021. It is now read-only.

DO NOT MERGE: Allow cluster members identified by DNS #90

Closed
wants to merge 1 commit into from
Closed

DO NOT MERGE: Allow cluster members identified by DNS #90

wants to merge 1 commit into from

Conversation

dghubble
Copy link
Contributor

These are the raw changes I needed for make for #89. These changes probably need to be gated behind a flag and are not intended to merge.

@@ -32,7 +32,6 @@ spec:
- --bind-address=0.0.0.0
- --secure-port=443
- --insecure-port=8080
- --advertise-address=$(MY_POD_IP)
Copy link
Contributor

Choose a reason for hiding this comment

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

IIRC this was because with vagrant/virtualbox the default interface is not routable between vms (I would need to re-verify this). Given that the vagrant support is only for local clusters, i'd be okay resolving this in some other way to make our manifests more generic.

@dghubble
Copy link
Contributor Author

dghubble commented Aug 24, 2016

Using a forked copy until NodeName is available in the downward api and bootkube can update to using that without breaking Vagrant examples.

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

Successfully merging this pull request may close these issues.

None yet

3 participants