kubernetes: do not strip binaries at build

Yocto/OE has its own way to control binary stripping. So don't do
it in the go build process. Otherwise, we'll get empty dbg packages.

Setting DBG=1 solves this problem, as stated in comments in the Makefile.
"""
  # Note: Specify DBG=1 for building unstripped binaries, which allows you to use code debugging
  # tools like delve. When DBG is unspecified, it defaults to "-s -w" which strips debug
  # information.
"""

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/recipes-containers/kubernetes/kubernetes_git.bb b/recipes-containers/kubernetes/kubernetes_git.bb
index 3a6e7119..8b7c9e06 100644
--- a/recipes-containers/kubernetes/kubernetes_git.bb
+++ b/recipes-containers/kubernetes/kubernetes_git.bb
@@ -87,7 +87,7 @@ do_compile() {
         export GOBIN=""
 
         # to limit what is built, use 'WHAT', i.e. make WHAT=cmd/kubelet
-        make cross CGO_FLAGS=${CGO_FLAGS} GO=${GO} KUBE_BUILD_PLATFORMS=${GOOS}/${GOARCH} GOLDFLAGS=""
+        make cross CGO_FLAGS=${CGO_FLAGS} GO=${GO} KUBE_BUILD_PLATFORMS=${GOOS}/${GOARCH} GOLDFLAGS="" DBG=1
 }
 
 do_install() {