Yuki Nishiwaki 2d275102b4 Check data is nil before executing mapping in os_info ...

This os_info mapper is used for v1.NodeStatus but
there is some case that mapper is evaluated when
v1.NodeStatus is nil.  For example, when the user try
to create v3.Node by calling API(POST /v3/nodes).

So we should check data is nil or not before executing
mapper in order to prevent from trying to use data(nil)
as map inside OSInfo.FromInternal

2018-08-02 21:20:54 -07:00

..

container_ports.go

Update ToInternal

2018-07-19 10:40:37 -07:00

container_probe.go

Refactor for IsEmpty

2018-07-19 10:40:37 -07:00

container_security_context.go

Update ToInternal

2018-07-19 10:40:37 -07:00

container_status.go

Assign state on init containers too

2018-07-19 10:40:37 -07:00

creator.go

Update ToInternal

2018-07-19 10:40:37 -07:00

env.go

Update ToInternal

2018-07-19 10:40:37 -07:00

init_container.go

Update ToInternal

2018-07-19 10:40:37 -07:00

namespace_reference.go

Update ToInternal

2018-07-19 10:40:37 -07:00

namespace.go

Update ToInternal

2018-07-19 10:40:37 -07:00

node_address.go

Update ToInternal

2018-07-19 10:40:37 -07:00

os_info.go

Check data is nil before executing mapping in os_info

2018-08-02 21:20:54 -07:00

persistvolumeclaim.go

Update ToInternal

2018-07-19 10:40:37 -07:00

scheduling.go

Update ToInternal

2018-07-19 10:40:37 -07:00

statefulset_spec.go

Update ToInternal

2018-07-19 10:40:37 -07:00

status.go

Update ToInternal

2018-07-19 10:40:37 -07:00

workload.go

Update ToInternal

2018-07-19 10:40:37 -07:00