#### 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>

2024-01-16 09:37:31 -05:00

2.6 KiB

Raw Blame History

layout

permalink

title

redirect_from

default

/development/

Development

/docs/development.md/

/docs/development/

Development Guide

Building Kompose

Read about building kompose here.

Workflow

Fork the main repository

Go to https://github.com/kubernetes/kompose
Click the "Fork" button (at the top right)

Clone your fork

The commands below require that you have $GOPATH. We highly recommended you put the Kompose code into your $GOPATH.

git clone https://github.com/$YOUR_GITHUB_USERNAME/kompose.git $GOPATH/src/github.com/kubernetes/kompose
cd $GOPATH/src/github.com/kubernetes/kompose
git remote add upstream 'https://github.com/kubernetes/kompose'

Create a branch and make changes

git checkout -b myfeature
# Make your code changes

Keeping your development fork in sync

git fetch upstream
git rebase upstream/main

Note: If you have write access to the main repository at github.com/kubernetes/kompose, you should modify your git configuration so that you can't accidentally push to upstream:

git remote set-url --push upstream no_push

Committing changes to your fork

git commit
git push -f origin myfeature

Creating a pull request

Visit https://github.com/$YOUR_GITHUB_USERNAME/kompose.git
Click the "Compare and pull request" button next to your "myfeature" branch.
Check out the pull request process for more details

Go Modules and dependency management

Kompose uses Go Modules to manage dependencies. If you want to introduce changes to dependencies, please ensure that go.mod and go.sum are updated properly.

Updating Kubernetes and OpenShift

Kubernetes version depends on what version is OpenShift using. OpenShift is using forked Kubernetes to carry some patches. Currently, it is not possible to use a different Kubernetes version from the version that OpenShift uses. (for more see comments in go.mod)

Adding CLI tests

Kompose CLI tests run kompose convert with compose files, and cross-check the k8s and OpenShift artifacts generated with the template files.

To generate CLI tests, please run make gen-cmd.

CI

For Kompose, we use numerous CI's:

TravisCI: Unit and CLI tests
SemaphoreCI: Integration / cluster tests
Fabric8CI: Secondary integration tests / future cluster tests

2.6 KiB Raw Blame History