OpenShift Documentation

The Knative (kn) CLI is a tool designed to simplify interaction with Knative components on OpenShift Serverless. It allows for managing serverless computing tasks through a concise command-line interface.

Key capabilities include:

• Deploying applications: Deploy serverless applications directly from the command line.
• Managing Knative Serving: Control services, revisions, and traffic-splitting.
• Managing Knative Eventing: Create and manage event sources and triggers.
• Sink Bindings: Create sink bindings to connect existing Kubernetes applications with Knative services.
• Extensibility: Use a flexible plugin architecture similar to kubectl to extend functionality.
• Autoscaling: Configure autoscaling parameters for Knative services.
• Automation: Support for scripted usage, such as waiting for operation results or implementing custom rollout and rollback strategies.

The Service Mesh includes several bundled add-ons for observability, management, and storage:

• Kiali: The management console providing dashboards, observability, and mesh topology visualization. It integrates with Prometheus and Jaeger.
• Prometheus: Used to store telemetry information from services. Kiali relies on Prometheus for metrics and health status.
• Jaeger: A traceability server used to centralize and display traces for requests moving between multiple services.
• Elasticsearch: A JSON-based search and analytics engine used by Jaeger for persistent storage.
• Grafana: Provides advanced query and metrics analysis dashboards for Istio data.

Supported Integrations

• 3scale: Integration with Red Hat 3scale API Management.
  • For versions prior to 2.1: Achieved via the 3scale Istio adapter.
  • For version 2.1 and later: Achieved via a WebAssembly module.

An {oke} subscription provides an enterprise-ready Kubernetes environment with the following capabilities:

• Automated Operations: Fully automated installers (IPI), customizable installers (UPI), and over-the-air smart upgrades.
• Security: Enterprise-secured Kubernetes using the same security context constraints (SCC), pod security policies, and SELinux integration as {product-title}.
• Management: Administrator web console, Operator Lifecycle Manager (OLM), and support for oc and kubectl.
• Networking: Full access to Kubernetes CNI, support for third-party SDNs, OVN Kubernetes overlay, Multus, and Kubernetes Network Policies. Includes HAProxy edge routing via the Route API.
• Storage: Support for all storage plugins supported by {product-title}.
• Virtualization: Support for Red Hat offerings derived from the kubevirt.io project.
• Monitoring: Integrated cluster monitoring based on Prometheus.
• Compatibility: Compatible with {rh-storage}, {quay}, and individual Red Hat Middleware products.

OpenShift Telemetry collects system, sizing, and usage information to assist with product improvement and support.

System Information

• Version & Updates: Cluster version, installed update details, update availability, update channels, image repositories, update progress, and update error counts.
• Identifiers: The unique random identifier generated during installation.
• Configuration: Node configuration at the cloud infrastructure level, hostnames, IP addresses, Kubernetes pod names, namespaces, and services.
• Component Status: Installed framework components and their condition/status, information about degraded software, and certificate validity.
• Operator Events: Events for all namespaces listed as "related objects" for a degraded Operator.
• Platform Details: The provider platform name and data center location.

Sizing Information

• Hardware/Resources: Cluster sizing, machine types, and machine-specific details (CPU cores and RAM usage).
• Virtualization: Number of running virtual machine instances (in virtual clusters).
• Storage/Scale: Number of etcd members and the number of objects stored in the etcd cluster.
• Builds: Number of application builds categorized by build strategy type (except in OpenShift Dedicated environments).

Usage Information

• Feature Usage: Information about components, features, and extensions.
• Preview/Unsupported Usage: Details regarding the use of Technology Previews and unsupported configurations.

Privacy and Data Security

Telemetry does not collect identifying information such as usernames or passwords. Red Hat does not intend to collect personal information. For more details, refer to the Red Hat Privacy Statement.

Using S2I provides several advantages over traditional Dockerfile-based builds:

• Reproducibility: Build environments are encapsulated in versioned container images, ensuring consistent results across continuous integration (CI) pipelines and making it easy to swap runtimes.
• Flexibility: Any Linux-based build system can be used. Scripts that process source code can be injected into builder images, allowing for easy adaptation of existing images.
• Speed: S2I encourages representing an application in a single image layer rather than building many incremental layers in a Dockerfile, which optimizes creation and deployment times.
• Security: Unlike standard Dockerfile builds which often run as root with broad network access, S2I builds can be launched within controlled container environments. When used with OpenShift, administrators can strictly control the privileges available to developers during the build process.