#### What type of PR is this?
<!--
Add one of the following kinds:
/kind bug
/kind cleanup
/kind feature
-->
/kind documentation
Updates the documentation to mention arm64.
#### 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)`.
-->
N/A
#### Special notes for your reviewer:
N/A
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>
#### What type of PR is this?
<!--
Add one of the following kinds:
/kind bug
/kind cleanup
/kind documentation
/kind feature
-->
update release script again with a reminder for docs update
#### What this PR does / why we need it:
#### 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 #
#### 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:
Updates the release script to use main instead of master
#### 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:
N/A
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
* feat: support custom build and push commands
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
* test: add functional tests of the support of custom build and push
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
* docs: add docs of the support of custom build and push
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
---------
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
* fix: support host port and protocol in functional tests
* feat: support compose.yaml and compose.yml files
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
* test: implement functional tests of the support of compose files
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
---------
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
* fix openshift dc and image stream api version
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
* e2e: Update Openshift manifests to update the API Version
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
---------
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
* feat: support security context fsgroup
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
* test: add unit test to security group fsgroup
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
* test: add functional test to security group fsgroup
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
* docs: add documentation of the new label of security group fsgroup
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
---------
Signed-off-by: AhmedGrati <ahmedgrati1999@gmail.com>
* feat: add the host port to containers
* test(unit): add unit tests for host port and protocol
* test(functional): add functional tests of host port and protocol
* test(functional): add functional tests of host port and protocol for openshift
* change master to main in scripts and docs
Changes the naming from master to main in the scripts and documentation.
Do not merge unless CI passes!
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
* remove 1.18, specify version of staticcheck
---------
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
Noticed a few errors in the release script when doing the 1.28.0 release
this month! So here is the updated script.
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
Maintenance!
Removes all the old scripts now used, and adds a "manual" doc sync
maintenance script which we have yet to automate.
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
* feat: migrate from libcompose to compose-go
libcompose has been deprecated since summer 2021 in favor of https://github.com/compose-spec/compose-go.
Kompose should now be able to load all versions of compose.
* chore: replace golint with staticcheck
golint has been deprecated. Recommended replacement is staticcheck.
* fix: make the out flag print to one file using seperator
* fix: comment an unused function
* fix: update test script
* fix: update output k8s
* fix: update the json output error condition
* fix: update envvars interpolation tests
* chore: update e2e tests to support yaml generation instead of JSON format
* fix: update e2e tests according to ci environment
* fix: apply PR changes
* Cleanup mentions about glide
* Don't use glide to ignore vendor directory
Since go-1.9, "./..." no longer contains the "vendor" directory.
Also, since #1305 migrated dependency management from glide to go mod,
there is no need to think about the "vendor" directory.
See: https://golang.org/doc/go1.9#vendor-dotdotdot
* go mod tidy
* allow port range specification in v1v2
* improve tests for loadPorts
* add port range to fixtures of docker-compose v2
* update fixtures to follow up on #1341
Updates the introduction doc and adds a synchornization script to be
manually run for website changes.
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
* Use go mod instead of glide
* Add `--with-kompose-annotation` flag to allow us to switch it off for tests
* Remove hostpid support (since the newest sdk does not support it)
* Create new test script and fixtures
* Remove replicationcontroller support
For some reason, Kubernetes tests haven't been running correctly. This
(hopefully) fixes it on Semaphore..
Signed-off-by: Charlie Drage <charlie@charliedrage.com>
1. fix the path used to read secret data
without this fix, the path to the compose file is added to the already
absolute path, hence readFile was unable to find the secrets file
2. fix the expected json format
mountPath includes the entire path including the name of the secret
* Copy the service labels also to Deployment Pod spec annotations
This allows kube2iam to work
* Remove test file forgotten from version 1.0.0
* Update test fixtures to have Deployment.spec.t.m.annotations
* Fix name conversion "test_server" -> "test-server"
It looks unrelated to my changes, but still changing.
* Fixing some more output fixtures
