forked from kubernetes/kompose
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pull] master from kubernetes:master #28
Open
pull
wants to merge
106
commits into
rizalgowandy:master
Choose a base branch
from
kubernetes:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Fix secret name error
Release 1.23.0
The label `kompose.service.accountname` defines the service account name to provide the credential info of the pod.
chore: update error for wrong volume type
Fix the selector field of service resource
fix: --build flag default change to local
Support custom registry on pushing image
fix daemonset creation (add selector)
* openSUSE meanwhile includes kompose in their official repositories for Tumbleweed and Leap * on SUSE Linux Enterprise Server kompose is available via PackageHub
Fixed secret file locations to match results from docker-compose when using file-based secrets
recommend to use 'go install @latest" for Go
…uration files (#1531) * fix: update kubernetes unit tests * fix: check whether selectors are present or not * fix: update golang-lint yaml file * fix: downgrade the version of fsouza go docker-client
* fix: update get container name function * test: add a test for the introduced fix
Signed-off-by: Charlie Drage <[email protected]> Signed-off-by: Charlie Drage <[email protected]>
don't need sync docs since we are building from `/docs` directory instead of `gh-pages`. Signed-off-by: Charlie Drage <[email protected]> Signed-off-by: Charlie Drage <[email protected]>
* fix all known trivy scan vulnerabilities * fix library issues: CVE-2022-27664, CVE-2022-32149, GHSA-69ch-w2m2-3vjp
* fix: update ingress class name assign
* 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
* 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.
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 <[email protected]> Signed-off-by: Charlie Drage <[email protected]>
Signed-off-by: Suraj Deshmukh <[email protected]> Signed-off-by: Suraj Deshmukh <[email protected]>
These were leftover files from a docs / site template. Removing as they are not needed. Signed-off-by: Charlie Drage <[email protected]> Signed-off-by: Charlie Drage <[email protected]>
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 <[email protected]> Signed-off-by: Charlie Drage <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )