[SRVCOM-3790] Unify Operator Admin/Dev perspective for Serverless

serving rewrite

functions rewrite

integrations, cli, observability rewrite

eventing section

qe feedback no1

qe feedback no2

pr feedback no1

mr feedback no1

mr feedback no2

mr feedback no3

mr feedback no4

Author: ochromy

_topic_maps/_topic_map.yml

@@ -217,10 +217,8 @@ Topics:
     File: create-domain-mapping
   - Name: Custom domains using the Knative CLI
     File: create-domain-mapping-kn
-  - Name: Domain mapping using the Developer perspective
+  - Name: Domain mapping using the web console
     File: domain-mapping-odc-developer
-  - Name: Domain mapping using the Administrator perspective
-    File: domain-mapping-odc-admin
   - Name: Securing a mapped service using a TLS certificate
     File: domain-mapping-custom-tls-cert
 - Name: High availability configuration for Knative Serving
@@ -250,8 +248,6 @@ Topics:
   Topics:
   - Name: Event sources overview
     File: knative-event-sources
-  - Name: Event source in the Administrator perspective
-    File: event-source-admin-perspective
   - Name: Creating an API server source
     File: serverless-apiserversource
   - Name: Creating a ping source
@@ -260,7 +256,7 @@ Topics:
     File: serverless-kafka-developer-source
   - Name: Custom event sources
     File: serverless-custom-event-sources
-  - Name: Connecting an event source to an event sink by using the Developer perspective
+  - Name: Connecting an event source to an event sink
     File: serverless-sink-source-odc
 - Name: Event sinks
   Dir: event-sinks
@@ -342,7 +338,7 @@ Topics:
     File: serverless-listing-event-sources
   - Name: Listing event source types from the command line
     File: list-event-source-types-cli
-  - Name: Listing event source types from the Developer perspective
+  - Name: Listing event source types from the web console
     File: list-event-source-types-odc
   - Name: Listing event sources from the command line
     File: list-event-sources-cli

eventing/brokers/serverless-using-brokers.adoc

@@ -18,7 +18,6 @@ include::modules/serverless-creating-broker-labeling.adoc[leveloffset=+1]
 include::modules/serverless-deleting-broker-injection.adoc[leveloffset=+1]
 // Creating brokers in the web console
 include::modules/serverless-creating-a-broker-odc.adoc[leveloffset=+1]
-include::modules/serverless-creating-broker-admin-web-console.adoc[leveloffset=+1]
 
 [id="next-steps_serverless-using-brokers"]
 == Next steps
@@ -29,4 +28,4 @@ include::modules/serverless-creating-broker-admin-web-console.adoc[leveloffset=+
 == Additional resources
 * xref:../../eventing/brokers/serverless-global-config-broker-class-default.adoc#serverless-global-config-broker-class-default[Configuring the default broker class]
 * xref:../../eventing/triggers/serverless-triggers.adoc#serverless-triggers[Triggers]
-* xref:../../eventing/brokers/serverless-using-brokers-managing-brokers.adoc#serverless-connect-sink-broker-odc_serverless-using-brokers-managing-brokers[Connect a broker to a sink using the Developer perspective]
+* xref:../../eventing/brokers/serverless-using-brokers-managing-brokers.adoc#serverless-connect-sink-broker-odc_serverless-using-brokers-managing-brokers[Connect a broker to a sink]

eventing/channels/connecting-channels-sinks.adoc

@@ -16,4 +16,4 @@ include::modules/serverless-creating-subscription-admin-web-console.adoc[levelof
 
 [id="next-steps_connecting-channels-sinks"]
 == Next steps
-* Configure xref:../../eventing/serverless-event-delivery.adoc#serverless-configuring-event-delivery-examples_serverless-event-delivery[event delivery parameters] that are applied in cases where an event fails to be delivered to an event sink.
+* Configure xref:../../eventing/serverless-event-delivery.adoc#serverless-configuring-event-delivery-examples_serverless-event-delivery[Event delivery] parameters that are applied in cases where an event fails to be delivered to an event sink.

eventing/channels/serverless-creating-channels.adoc

@@ -9,7 +9,6 @@ toc::[]
 include::snippets/serverless-channels-intro.adoc[]
 
 // Channel
-include::modules/serverless-creating-channel-admin-web-console.adoc[leveloffset=+1]
 include::modules/serverless-create-channel-odc.adoc[leveloffset=+1]
 include::modules/serverless-create-channel-kn.adoc[leveloffset=+1]
 include::modules/serverless-create-default-channel-yaml.adoc[leveloffset=+1]

eventing/discovery/list-event-source-types-odc.adoc

@@ -1,7 +1,7 @@
 :_content-type: ASSEMBLY
 include::_attributes/common-attributes.adoc[]
 [id="list-event-source-types-odc"]
-= Listing event source types from the Developer perspective
+= Listing event source types from the web console
 :context: list-event-source-types-odc
 
 

eventing/discovery/serverless-listing-event-sources.adoc

@@ -6,4 +6,4 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-It is possible to view a list of all event sources or event source types that exist or are available for use on your {ocp-product-title} cluster. You can use the Knative (`kn`) CLI or the *Developer* perspective in the {ocp-product-title} web console to list available event sources or event source types.
+It is possible to view a list of all event sources or event source types that exist or are available for use on your {ocp-product-title} cluster. You can use the Knative (`kn`) CLI or the {ocp-product-title} web console to list available event sources or event source types.

eventing/event-sources/knative-event-sources.adoc

@@ -8,7 +8,7 @@ toc::[]
 
 A Knative _event source_ can be any Kubernetes object that generates or imports cloud events, and relays those events to another endpoint, known as a xref:../../eventing/event-sinks/serverless-event-sinks.adoc#serverless-event-sinks[_sink_]. Sourcing events is critical to developing a distributed system that reacts to events.
 
-You can create and manage Knative event sources by using the *Developer* perspective in the {ocp-product-title} web console, the Knative (`kn`) CLI, or by applying YAML files.
+You can create and manage Knative event sources in the {ocp-product-title} web console, the Knative (`kn`) CLI, or by applying YAML files.
 
 Currently, {ServerlessProductName} supports the following event source types:
 
@@ -19,3 +19,6 @@ xref:../../eventing/event-sources/serverless-pingsource.adoc#serverless-pingsour
 xref:../../eventing/event-sources/serverless-kafka-developer-source.adoc#serverless-kafka-developer-source[Kafka event source]:: Connects an Apache Kafka cluster to a sink as an event source.
 
 You can also create a xref:../../eventing/event-sources/serverless-custom-event-sources.adoc#serverless-custom-event-sources[custom event source].
+
+// Event sources
+include::modules/serverless-creating-event-source-admin-web-console.adoc[leveloffset=+1]

eventing/event-sources/serverless-sink-source-odc.adoc

@@ -1,7 +1,7 @@
 :_content-type: ASSEMBLY
 include::_attributes/common-attributes.adoc[]
 [id="serverless-sink-source-odc"]
-= Connecting an event source to an event sink by using the Developer perspective
+= Connecting an event source to an event sink
 :context: serverless-sink-source-odc
 
 When you create an event source by using the {ocp-product-title} web console, you can specify a target event sink that events are sent to from that source. The event sink can be any addressable or callable resource that can receive incoming events from other resources.

eventing/subscriptions/serverless-subs.adoc

@@ -9,7 +9,6 @@ toc::[]
 After you have created a channel and an event sink, you can create a subscription to enable event delivery. Subscriptions are created by configuring a `Subscription` object, which specifies the channel and the sink (also known as a _subscriber_) to deliver events to.
 
 // Subscription
-include::modules/serverless-creating-subscription-admin-web-console.adoc[leveloffset=+1]
 include::modules/serverless-creating-subscriptions-odc.adoc[leveloffset=+1]
 include::modules/serverless-creating-subscriptions-yaml.adoc[leveloffset=+1]
 include::modules/serverless-creating-subscriptions-kn.adoc[leveloffset=+1]

eventing/triggers/create-triggers.adoc

@@ -67,9 +67,6 @@ You can save the configuration to a file, for example, `custom-path-trigger.yaml
 $ oc apply -f custom-path-trigger.yaml
 ----
 
-// Trigger
-include::modules/serverless-creating-trigger-admin-web-console.adoc[leveloffset=+1]
-
 // ODC
 include::modules/serverless-create-trigger-odc.adoc[leveloffset=+1]