Skip to content

Latest commit

 

History

History
60 lines (43 loc) · 2.42 KB

rolling_updates_from_jenkins.md

File metadata and controls

60 lines (43 loc) · 2.42 KB
Raw

###How To For our example, Jenkins is set up to have one build step in bash:

Jenkins "Bash" build step

    #!/bin/bash
    cd $WORKSPACE
    source bin/jenkins.sh
    source bin/kube-rolling.sh

Our project's build script (bin/jenkins.sh), is followed by our new kube-rolling script. Jenkins already has $BUILD_NUMBER set, but we need a few other variables that are set in jenkins.sh that we reference in kube-rolling.sh:

    DOCKER_IMAGE="path_webteam/public"
	REGISTRY_LOCATION="dockerreg.web.local/"

Jenkins builds our container, tags it with the build number, and runs a couple rudimentary tests on it. On success, it pushes it to our private docker registry. Once the container is pushed, it then executes our rolling update script.

kube-rolling.sh

    #!/bin/bash
    # KUBERNETES_MASTER: Your Kubernetes API Server endpoint
    # BINARY_LOCATION:   Location of pre-compiled Binaries (We build our own, there are others available)
    # CONTROLLER_NAME:   Name of the replicationController you're looking to update
    # RESET_INTERVAL:    Interval between pod updates

    export KUBERNETES_MASTER="http://10.1.10.1:8080"
    BINARY_LOCATION="https://build.web.local/kubernetes/"
    CONTROLLER_NAME="public-frontend-controller"
    RESET_INTERVAL="10s"

    echo "*** Time to push to Kubernetes!";

    #Delete then graba kubecfg binary from a static location
    rm kubecfg
    wget $BINARY_LOCATION/kubecfg

    echo "*** Downloaded binary from $BINARY_LOCATION/kubecfg"

    chmod +x kubecfg

    # Update the controller with your new image!
    echo "*** ./kubecfg -image \"$REGISTRY_LOCATION$DOCKER_IMAGE:$BUILD_NUMBER\" -u $RESET_INTERVAL rollingupdate $CONTROLLER_NAME"
    ./kubecfg -image "$REGISTRY_LOCATION$DOCKER_IMAGE:$BUILD_NUMBER" -u $RESET_INTERVAL rollingupdate $CONTROLLER_NAME

Though basic, this implementation allows our Jenkins instance to push container updates to our Kubernetes cluster without much trouble.

Notes

When using a private docker registry as we are, the Jenkins slaves as well as the Kubernetes minions require the .dockercfg file in order to function properly.

Questions

twitter @jeefy

irc.freenode.net #kubernetes jeefy

Analytics