Skip to content
This repository was archived by the owner on Feb 22, 2022. It is now read-only.
This repository was archived by the owner on Feb 22, 2022. It is now read-only.

Broker selection fields on install #175

@matzew

Description

@matzew

Problem

0.14 will come with two brokers:

  • channel based
  • multitenant channel broker

There are now different artifacts, that we need to take into account.

We have two convenient release yamls:

However, that means you pick one or the other.

Generally the artifacts we ship are:

  • eventing-crds.yaml
  • eventing-core.yaml
  • channel-broker.yaml
  • mt-channel-broker.yaml

How about we have the operator to apply the first two yamls, and based on installation choice (or later updated CR), we pick which broker we apply?

The default would be channel,

apiVersion: operator.knative.dev/v1alpha1
kind: KnativeEventing
metadata:
  name: knative-eventing
  namespace: knative-eventing
spec:
  broker: channel

Persona:
Which persona is this feature for?

  • System integrator

Exit Criteria

installation of broker done, based on broker field

Time Estimate (optional):
How many developer-days do you think this may take to resolve?

Additional context (optional)
Add any other context about the feature request here.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions