You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by ssisk <gi...@git.apache.org> on 2017/05/22 18:44:01 UTC
[GitHub] beam pull request #3196: [BEAM-2342] Cleanup k8s scripts naming & don't crea...
GitHub user ssisk opened a pull request:
https://github.com/apache/beam/pull/3196
[BEAM-2342] Cleanup k8s scripts naming & don't create insecure svc by default
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`.
- [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](https://www.apache.org/licenses/icla.pdf).
---
These scripts setup a internet-accessible service by default, which is
insecure since we rely on firewalls for securing the data stores.
R: @tgroh
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ssisk/beam secure-k8s-es
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/3196.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3196
----
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] beam pull request #3196: [BEAM-2342] Cleanup k8s scripts naming & don't crea...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/beam/pull/3196
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---