Overview

Currently, the CLI supports creation of Cloud Function. Currently in Topology, functions are currently displayed as Knative Services. We should have a way to quickly identify a function in topology. Functions can be identified by specific labels.

Additionally, we need to support ability to the use case where a function (KSVC) can connect to an event source which can connect to a Managed Service. The main AI here is to verify if ServiceBinding works with managed service and kafka source

Exploration Results

Jamboard from exploration

Acceptance Criteria

1. In Topology, functions should look visually different from a Knative Service
   1. The grouping color of a function is purple, rather than grey
   2. Use a functions icon to the left of the KSVC badge, rather than Knative icon
2. As a user, I should be able to differentiate between a plain Knative Service and a Serverless Function when looking at the Details page of the KSVC AND the details tab of the side panel in Topology
3. Improved integration of Managed Services with Kafka source
   1. In topology only for KafkaSouce, a Managed Kafka Connection (MKC) will be a valid target (like connector) i,e ability to create a connector only on Kafka Source with MKC as valid target and on dropping on MKC should update KafkaSource with SASL secrets , TLS enabled and bootstrap server (will be handling this with logic is UI as SBR is not meant for it, just as we update sink for any sources currently).
   2. In the Kafka Source creation form, show type ahead with bootstrap server from MKC if the project has MKC and user has access to them

Design Artifacts

tbd

Slack Channel

tbd

Notes

• Managed Service piece is Tech Preview
• Serverless Function piece is Dev Preview