search

jenkins-x / enhancements

Repository containing design proposals for Jenkins X enhancements
12 stars 16 forks source link

helm 3 and kustomize support #34

Closed jstrachan closed 3 years ago

jstrachan commented 4 years ago

we are restarting the previous work in OSS to get helm 3 and/or kustomize supporter in Jenkins X along with improving the boot UX & GitOps support along with multi cluster.

Some associated notes and docs:

polothy commented 4 years ago

along with multi cluster

💯 💯 💯 💯 💯 💯

Are there currently any recommendations on how to handle multiple team environments in a single cluster? Before we were installing a new JX into the cluster for every team so they could have their own environments to promote into. It sounds like with boot we shouldn't do that and install boot once... but unsure how to manage multiple teams. Maybe just make no environments with auto-promotion and teams just promote to their envs?

jstrachan commented 4 years ago

@polothy this will all become clear pretty soon when we start documenting / demoing the PoC but we are currently thinking of 1 git repository per cluster where you can define all the namespaces and resources you want to install in that cluster.

So if you want, say, 3 teams to share a cluster you could have some common namespaces with shared stuff...

Then each team could have its own namespaces for dev and/or staging where pipelines would run and stuff.

Then you'd just have 1 git repository to configure for all the namespaces/components in your cluster

There's a few ways to configure all this - e.g. each team gets their own local tekton/lighthouse versions they can use that only work within that namespace; or there's a shared namespace with those things that all teams use.

polothy commented 4 years ago

Thanks, we will try to do that and see where we land.

jenkins-x-bot commented 3 years ago

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. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

jenkins-x-bot commented 3 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle rotten

jenkins-x-bot commented 3 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten. Provide feedback via https://jenkins-x.io/community. /close

jenkins-x-bot commented 3 years ago

@jenkins-x-bot: Closing this issue.

In response to [this](https://github.com/jenkins-x/enhancements/issues/34#issuecomment-751423462): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. >Provide feedback via https://jenkins-x.io/community. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [jenkins-x/lighthouse](https://github.com/jenkins-x/lighthouse/issues/new?title=Command%20issue:) repository.