travisn cb82f36eba ceph: no need for --public-bind-addr with host networking ...

The mons require the --public-bind-addr when host networking is not in use
since the pod ip will be different from the service ip that will be
advertised to clients. When host networking is enabled, there is no
need for this argument since the endpoints will be the same to bind
inside the pod as what is advertised to clients.

Signed-off-by: travisn <tnielsen@redhat.com>

2019-05-10 15:07:46 -06:00

..

config.go

ceph mds: configure completely from operator

2019-02-28 12:31:43 -07:00

endpoint_test.go

ceph mons: set up entirely in operator

2019-02-05 06:19:59 -07:00

endpoint.go

ceph mons: set up entirely in operator

2019-02-05 06:19:59 -07:00

env.go

Ceph messengers 2 support

2019-02-22 00:09:37 +01:00

health_test.go

update to the k8s 1.14 client libraries

2019-04-18 07:51:41 -06:00

health.go

ceph: simplify the ceph command execution interface

2019-05-06 10:10:05 -07:00

mon_test.go

ceph: expose /var/log/ceph to the host

2019-04-15 10:47:09 +02:00

mon.go

Ceph: fix upgrade to Nautilus

2019-04-24 10:57:29 +02:00

node_test.go

ceph: no need for --public-bind-addr with host networking

2019-05-10 15:07:46 -06:00

node.go

update to the k8s 1.14 client libraries

2019-04-18 07:51:41 -06:00

service.go

ceph: mon service forwards default bind port 6789

2019-04-03 15:53:56 -06:00

spec_test.go

ceph: implement pod restriction on memory

2019-03-15 17:35:44 +01:00

spec.go

ceph: no need for --public-bind-addr with host networking

2019-05-10 15:07:46 -06:00

util.go

Ceph messengers 2 support

2019-02-22 00:09:37 +01:00