beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ssisk <>
Subject [GitHub] beam pull request #2431: [BEAM-1882] Update postgres k8 scripts & add script...
Date Wed, 05 Apr 2017 00:16:07 GMT
GitHub user ssisk opened a pull request:

    [BEAM-1882] Update postgres k8 scripts & add scripts for running local dev test

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [X] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [X] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [X] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [X] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    Currently, the postgres instance created is a pod - that means that if crashes/anything
happens to it, it won't be re-created. We should should switch to ReplicaController, which
will ensure that it will be automatically created again.
    This change:
    * consolidates the normal pod creation + service down to one file
    * switches from pods -> replica controllers
    * adds a k8s script that exposes a public IP - this can be used when doing local development.
    cc @jbonofre @jasonkuster 

You can merge this pull request into a Git repository by running:

    $ git pull jdbc-it-k8-scripts

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2431
commit 01e00ccb8b4c7ab9c80fc2a4f2c0205b1af0d5bc
Author: Stephen Sisk <>
Date:   2017-03-17T22:09:00Z

    Update postgres k8 scripts & add scripts for running local dev test


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message