- Documentation
- OpenShift Dedicated
- Serverless
- Eventing
- Event sources
- Event source in the Administrator perspective history bug_report picture_as_pdf
- About
- Introduction to OpenShift Dedicated
- Red Hat OpenShift Cluster Manager
- Planning your environment
- Getting started
- Installing, accessing, and deleting OpenShift Dedicated clusters
- Cluster administration
- Security and compliance
- Authentication and authorization
- Upgrading
- CI/CD
- Add-on services
- Storage
- Registry
- Networking
- Applications
-
Logging
- Release notes
- About Logging
- Installing Logging
- Accessing the service logs
-
Configuring your Logging deployment
- About the Cluster Logging custom resource
- Configuring the logging collector
- Configuring the log store
- Configuring the log visualizer
- Configuring Logging storage
- Configuring CPU and memory limits for Logging components
- Using tolerations to control Logging pod placement
- Moving the Logging resources with node selectors
- Maintenance and support
- Logging with the LokiStack
- Viewing logs for a specific resource
- Viewing cluster logs in Kibana
- Forwarding logs to third party systems
- Enabling JSON logging
- Collecting and storing Kubernetes events
- Updating Logging
- Viewing cluster dashboards
- Troubleshooting Logging
- Uninstalling Logging
- Exported fields
- Monitoring user-defined projects
-
Serverless
- Release notes
- About Serverless
- Installing Serverless
- Knative Serving
-
Eventing
- Knative Eventing
- Event sources
- Event sinks
- Brokers
-
Triggers
- Triggers overview
- Creating triggers from the web console
- Creating triggers from the command line
- Creating a trigger from the Administrator perspective
- List triggers from the command line
- Describe triggers from the command line
- Connecting a trigger to a sink
- Filtering triggers from the command line
- Updating triggers from the command line
- Deleting triggers from the command line
- Channels
- Subscriptions
- Event discovery
- Tuning eventing configuration
- kn-event plugin
-
Functions
- Setting up OpenShift Serverless Functions
- Getting started with functions
- Developing Quarkus functions
- Developing Node.js functions
- Developing TypeScript functions
- Using functions with Knative Eventing
- Function project configuration in func.yaml
- Accessing secrets and config maps from functions
- Adding annotations to functions
- Functions development reference guide
- Knative CLI
- Administer
- Security
- Observability
- Removing Serverless
- Serverless support
- Troubleshooting
Event source in the Administrator perspective
Sourcing events is critical to developing a distributed system that reacts to events.
Creating an event source by using the Administrator perspective
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 sink.
-
The OpenShift Serverless Operator and Knative Eventing are installed on your OpenShift Dedicated cluster.
-
You have logged in to the web console and are in the Administrator perspective.
-
You have cluster or dedicated administrator permissions for OpenShift Dedicated.
-
In the Administrator perspective of the OpenShift Dedicated web console, navigate to Serverless → Eventing.
-
In the Create list, select Event Source. You will be directed to the Event Sources page.
-
Select the event source type that you want to create.