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

ROADMAP.md: update it to reflect 2022 goals #665

Merged
merged 1 commit into from
Mar 9, 2022
Merged

ROADMAP.md: update it to reflect 2022 goals #665

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
53 changes: 21 additions & 32 deletions ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,5 @@
# Roadmap

## Towards seamless upgrades

Support seamless upgrades from a version to another. This mean being
able to update some object pre-reconcile (upgrade) if need be (in case
of deprecated fields, …).

## Driving adoption

- Add more docs, and have it publish as part of the tekton.dev/docs
Expand All @@ -16,39 +10,14 @@ of deprecated fields, …).
An acceptance criteria for this would be to use the operator in our
own CI (aka dogfooding).

## Pipeline

### Support feature flags

Support setting feature flags, such as:

- Affinity Assistant
- Custom Tasks
- API feature flag (stable, …)

### Support configuration options

Support configuration options of `tektoncd/pipeline`, such as:

- Support managing the content of pipeline's configmap (default, …)
- Enabling/configuring High availability

## Triggers

- Ship and configure custom interceptors (built-in, from experimental,
…)
- Multi-tenant eventlistener support

## New Component integration

As of today, the operator is capable of installing Pipeline, Triggers
and the dasbhoard. We may want to support shipping more components

### Components

- results
- chains
- self-hosted hub
- New "graduated" components

### Experimental projects

Expand All @@ -60,6 +29,16 @@ and the dasbhoard. We may want to support shipping more components
Today, we are shipping ClusterTask only for the OpenShift target. We
should aim towards shipping this for all targets (k8s, …)

## Tekton CLI integration

User should be able to get `tkn` and install, upgrade and manage the
operator lifecycle directly from it. *This should help adoption as well*.
Comment on lines +34 to +35
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍


## Support rollback

In case of a failed upgrade, it should be possible to roll-back into
the previous known good state.

## More targets

We are currently targeting and releasing only two target:
Expand All @@ -70,6 +49,16 @@ We should aim to support more, starting with GKE. GKE is a easy target
as we could use this in dogfooding. An idea of what could be specific
for GKE is around the ingress configuration, …

## More tests, more confidence

The operator codebase integrates all tektoncd component into one
place, it is a critical piece and need to be heavily tested so that we
feel confident to release it.

- Upgrade tests
- Running component tests on top of an operator installation
- etc…

## Releases

- Automated relases
Expand Down