Remove ExplicitStart* vars, rework --kubeconfig handling #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged by openshift-bot
Merged by openshift-bot
Merged by openshift-bot
Merged by openshift-bot
Merged by openshift-bot
liggitt
changed the title
liggitt
changed the title
Require --kubernetes host and --kubeconfig host to match Shorten --write-config flag name Limit kubeconfig loading to --kubeconfig flag only (no env or $HOME lookup) Change node to use --kubernetes address (which falls back to --master if unspecified) Restore previous behaviors: * default to local IP as --master, even for start node * allow running with --kubernetes without --kubeconfig Derive etcd bind addr
deads2k
pushed a commit
that referenced
this pull request
Mar 11, 2015
Fix bindata for rework page structure to use flexbox so that sidebar col...
deads2k
pushed a commit
that referenced
this pull request
Nov 16, 2015
Updating the contributing doc to use real examples for commands. Initially it is helpful to be able to run these and trust your system will be setup properly. More advanced users will know how to modify. - rearranging instructions, move to start openshift from vagrant home dir - Add instructions for updating $PATH to binaries - updating contrib w/fixtures sample code - update openshift start command to use `which openshift` - remove --volumes-dir - Update dir under vangrant #10 registry instructions - update note: add to .bash_proflie - update OPENSHIFT_MEMORY to 4192 to resolve make clean build errs - move the vagrant box remove tip up to #4
deads2k
pushed a commit
that referenced
this pull request
May 17, 2016
Add ose-docker-registry to ose-build script
deads2k
pushed a commit
that referenced
this pull request
Jul 6, 2016
init minion registry for sync mode, updated README for sync mode
deads2k
pushed a commit
that referenced
this pull request
Jul 6, 2016
Docker-only containers (eg, "docker run foobar") get attached to lbr0, and their traffic flows from lbr0 -> vlinuxbr -> vovsbr -> br0. To ensure that docker-only containers can access the rest of the world through tun0, we need to pass their traffic along instead of dropping it in table #3: cookie=0x0, duration=12307.238s, table=0, n_packets=292, n_bytes=23330, actions=learn(table=7,hard_timeout=900,priority=200,NXM_OF_ETH_DST[]=NXM_OF_ETH_SRC[],load:NXM_NX_TUN_IPV4_SRC[]->NXM_NX_TUN_IPV4_DST[],output:NXM_OF_IN_PORT[]),goto_table:1 cookie=0x0, duration=12307.227s, table=1, n_packets=165, n_bytes=13199, actions=goto_table:3 <drop due to no match> Add a rule allowing traffic from vovsbr to jump from table #3 to table #4, where it will get directed to the right place (either other pods or tun0).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.