#### What type of PR is this?
<!--
Add one of the following kinds:
/kind bug
/kind cleanup
/kind documentation
-->
/kind feature
#### What this PR does / why we need it:
This changes our example to use non-root so it runs well on non-root
clusters (ex. openshift).
We also add debugging tools so we can safely explore the container.
/tmp is also added as the directory for the replica or else it fails.
#### Which issue(s) this PR fixes:
<!--
*Automatically closes linked issue when PR is merged.
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
N/A
#### Special notes for your reviewer:
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
#### What type of PR is this?
<!--
Add one of the following kinds:
/kind bug
/kind documentation
/kind feature
-->
/kind cleanup
#### What this PR does / why we need it:
Fixes the current broken examples by:
* Removing all the old incompatible ones (we do not really support v3
anymore or v2... since switching libraries)
* Uses quay.io/kompose/web as our front end example which is a fork of
the guestbook-go kubernetes examples
#### Which issue(s) this PR fixes:
<!--
*Automatically closes linked issue when PR is merged.
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
Closes https://github.com/kubernetes/kompose/issues/1757
#### Special notes for your reviewer:
Test using docker-compose (you'll see it come up!), then try with
kompose :)
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
#### What type of PR is this?
<!--
Add one of the following kinds:
/kind bug
/kind cleanup
/kind documentation
/kind feature
-->
We should be using replica to indicate a new node of redis.
Unfortunatley gcr still hasn't pushed another image, so we will still
have to use registry.k8s.io/redis-slave:v2
#### What this PR does / why we need it:
N/A
#### Which issue(s) this PR fixes:
<!--
*Automatically closes linked issue when PR is merged.
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
-->
Fixes #
N/A
#### Special notes for your reviewer:
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
This adds support for building and pushing docker containers
when you perform either `kompose convert` or `kompose up`.
Docker Compose files who have build parameters with their respective
image and build keys will automatically be both built and pushed.
* This PR adds functional tests for kompose up/down. The test scripts
are hosted under script/test_in_openshift. The directory structure,
as follows:
script/test_in_openshift/
├── compose-files
│ └── docker-compose-command.yml
├── lib.sh
├── run.sh
└── tests
├── buildconfig.sh
├── entrypoint-command.sh
├── etherpad.sh
└── redis-replica-2.sh
* script/test_in_openshift/run.sh is the master script
which executes all the tests
* script/test_in_openshift/lib.sh consists of helper functions
for `kompose up` and `kompose down` checks
* script/test_in_openshift/tests directory consists of test scripts
* The scripts use 'oc cluster up' for setting up a single-machine
OpenShift cluster. It exits if oc binaries are not installed
* Most of the docker compose files used are the ones already
available in examples/ or script/test/fixtures.
* How to run the tests: 'make test-openshift'
Moves `docker-compose.yaml` to `docker-compose-counter.yaml` and
replaces the default docker-compose.yaml with the example from the
Kompose.io website.
We also rename each file from yml to yaml.
As well as do some slight modifications / formatting to
docker-compose-bundle.dab
This commit updates a few sentences in the README that I thought would
need improving.
Bundles now end with the .dab extension and are named "Distributed
Application Bundles" now. I've updated the README as well as the example
accordingly.
Charlie Drage
vaibhav2107
namusyaka
Tim Hockin
Suraj Narwade
Tomas Kral
Anush Shetty
Ratnadeep Debnath
Suraj Deshmukh
Tuna
runseb
Janet Kuo