Skip to content
This repository was archived by the owner on Dec 16, 2021. It is now read-only.
This repository was archived by the owner on Dec 16, 2021. It is now read-only.

[FEATURE REQUEST]: Separate release yaml for kafka trigger controller #31

Description

@aeryaguzov

Is this a BUG REPORT or FEATURE REQUEST?:

FEATURE REQUEST

What happened:

In the release page we have only one yaml that installs kafka trigger together with kafka in the same k8s cluster. However it is suitable only for development purposes. Common approach is described here: https://kubeless.io/docs/use-existing-kafka/

I would like to have special yaml that will install ONLY kafka trigger (RBAC/NON-RBAC) because it will allow to programmatically provision k8s cluster from github release page using kubectl create

What you expected to happen:

Separate YAML for kafka trigger and separate YAML for kafka.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions