Comments (4)
yes kubernetes support is added only in next and will be published with v1.0.0
the docs shold also reflect that ...
for now you need to use next .
PS: you can pin next by next-someCommitID[10]
as for the chart ... I think you used the stable tag witch resulted in this ... well chart related issues are now tracked in our chart repo :)
from helm.
yes kubernetes support is added only in next and will be published with v1.0.0
the docs shold also reflect that ...
for now you need to use next . PS: you can pin next by next-
someCommitID[10]
Exactly what I did!
as for the chart ... I think you used the stable tag witch resulted in this ... well chart related issues are now tracked in our chart repo :)
I used the default, yes.
from helm.
It works with Kubernetes for me.
➜ cat ../values.yaml
---
server:
image:
tag: next-3033abc3b4
[...]
agent:
image:
tag: next-3033abc3b4
[...]
Then
helm repo add woodpecker https://woodpecker-ci.org/
helm repo update
helm upgrade --install --atomic woodpecker --namespace woodpecker woodpecker/woodpecker -f values.yaml --version 0.1.5
Of course it should also work with tag: next
.
Note for maintainers : if you do not specify --version 0.1.5
it will download highest version (not latest) which is 0.15.6
or something similar.
from helm.
#45 will solve the versioning. Apart from that next can be used and 1.0.0 should be released soonishly
from helm.
Related Issues (20)
- overwrite nodeSelector for jobs HOT 2
- `ErrImagePull` because the tag from `appVersion` doesn't actually exist HOT 2
- feat: support `initContainers` for server
- Bad indent setting for extraVolumes? HOT 5
- OCI Chart Not Published HOT 3
- clone step using RWX volume takes long time to complete HOT 8
- List of registered agents grows indefinitelly HOT 2
- Can't upgrade to 1.1.0 using helm controller HOT 2
- Secret generation causes issues for GitOps approach HOT 4
- Disabling agent persistence renders invalid StatefulSet HOT 1
- Helm template error when upgrading to 1.2.x
- Server pod errors out on fresh installation: could not setup service manager: forge not configured HOT 5
- Add a testing framework? HOT 1
- Documentation for installing current release? HOT 2
- Remove `.cr-index/index.yaml`
- missing secret HOT 3
- agent defaults fail: "woodpecker-server.<namespace>.svc.cluster.local: no such host"
- Ability to add additional volumes to the server HOT 3
- Dependency Dashboard
- allow `extraVolumeMounts` without enabling default persistentVolume HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from helm.