Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create a client tool release #3

Closed
bgrant0607 opened this issue May 26, 2016 · 8 comments
Closed

Create a client tool release #3

bgrant0607 opened this issue May 26, 2016 · 8 comments
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@bgrant0607
Copy link
Member

bgrant0607 commented May 26, 2016 •
edited
Loading

Addon components get updated in Kubernetes clusters by updating manifests referring to new image tags. The images don't need to be bundled directly with the Kubernetes release because they are just pulled from the registry.

Tools, however, typically can't be pulled in that way. However, we would like to make it easy for users to get popular tools. Helm is a prime candidate. It should be ready for bundling with K8s 1.4. Kompose is another possibility.

cc @technosophos @sebgoa
@bgrant0607
Copy link
Member Author

cc @pwittrock

@pwittrock
Copy link
Member

Would this include upgrading bundled tools when upgrading releases?

@bgrant0607
Copy link
Member Author

@pwittrock We'd ship the latest release of each tool. We don't provide an installer. The distros do that.

@bgrant0607 bgrant0607 mentioned this issue Jul 19, 2016
Closed
This was referenced Oct 21, 2016
Closed
Closed
@bgrant0607 bgrant0607 changed the title Bundle community tools with releases Create a client tool release Mar 23, 2017
@bgrant0607 bgrant0607 mentioned this issue Apr 15, 2017
Closed
@bgrant0607
Copy link
Member Author

cc @monopole

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 25, 2017
@bgrant0607
Copy link
Member Author

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 22, 2018
@dims
Copy link
Member

dims commented Oct 23, 2018

/close

totally stale issue

@k8s-ci-robot
Copy link
Contributor

@dims: Closing this issue.

In response to this:

/close

totally stale issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

marpaia pushed a commit to marpaia/release that referenced this issue Feb 21, 2019
Merge pull request kubernetes#3 from kubernetes/master
7ad1edb 
Update 4/24/18 release notes
@justaugustus justaugustus added sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-eng Issues or PRs related to the Release Engineering subproject labels Dec 9, 2019
k8s-ci-robot pushed a commit that referenced this issue Apr 20, 2022
@saschagrunert
Fix fastforward git user configuration
814e655 
The recent git auto fast forward jobs fails because of the misconfigured
git user:

https://storage.googleapis.com/kubernetes-jenkins/logs/ci-fast-forward/1516649755411746816/build-log.txt

```
Step #3: level=info msg="Merging main branch changes into release branch"
Step #3: level=fatal msg="merge main ref: run git merge: command /usr/bin/git merge -X ours origin/master did not succeed: Committer identity unknown\n\n*** Please tell me who you are.\n\nRun\n\n  git config --global user.email \"you@example.com\"\n  git config --global user.name \"Your Name\"\n\nto set your account's default identity.\nOmit --global to set the identity only in this repository.\n\nfatal: unable to auto-detect email address (got 'root@c96ac26cb82d.(none)')\n"
Finished Step #3
ERROR
```

We now fix this by doing the same configuration like we do in krel
stage and release.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@dims @justaugustus @bgrant0607 @pwittrock @k8s-ci-robot @fejta-bot