WIP: Knative 0.1.0 release notes draft

[illume]

Draft notes

TODO: short description what knative is, what this plugin is and provides

traffic splitting

TODO: Short description... screenshot

autoscaling configuration

TODO: Short description... screenshot

networking details (Domain Mappings, HTTPRoutes)

TODO: Short description... screenshot

Edit/Read mode toggle to the Headlamp UI

TODO: Short description... screenshot

All Commits

Commit	Author	Message
f0c939b2e	@kahirokunn	knative: Init knative plugin
d0da320d4	@kahirokunn	knative: Add docs and ArtifactHub metadata
e644e5ff2	@kahirokunn	knative: Add cluster selection and install check
92441aab7	@kahirokunn	knative: Define Knative resource classes
661fd0dba	@kahirokunn	knative: Add common UI utilities
00531a596	@kahirokunn	knative: Add KService list and detail views
d2f384b1a	@kahirokunn	knative: Add networking overview
d968d8e36	@kahirokunn	knative: Register routes and sidebar entries
c701e0d2e	@kahirokunn	knative: fix linting issues and apply code formatting
75b32e45f	@kahirokunn	README.md: Add knative to plugin list
9c1e435cf	@kahirokunn	knative: Add permission checks
e0512f596	@kahirokunn	knative: Add copyright headers
b5284dc3e	@kahirokunn	knative: Add missing CRD printer columns
9fdd18e7a	@skoeva	Bump tar to 7.5.3
9734acc9b	@skoeva	Bump lodash to 4.17.23
12ea48a7d	@mudit06mah	knative: Fix package name
4ca0c1eb6	@intojhanurag	knative: utils: time: nullable: Add unit tests
831971d99	@intojhanurag	knative: kservices/List: Memoize the headerProps and actions to reduce renders
ae9388aee	@Sbragul26	frontend: knative: memoize ResourceListView props
2dc52888f	@mudit06mah	knative: kservices: Shift conditions section to common components
b03d60a0a	@mudit06mah	knative: revisions: Add revisions list & detail view, revisions sidebar entry
2e37e92e9	@mudit06mah	knative: common: Refactor condition table
4107ef45d	@mudit06mah	knative: kservice: Refactor kservice sections and add info

Contributors

Thanks to all the contributors who made this release possible!

@kahirokunn, @mudit06mah, @intojhanurag, @Sbragul26, @skoeva, @illume, @joaquimrocha

[mudit06mah]

Knative

Knative provides powerful serverless capabilities to Kubernetes, such as scale to zero, revision-based deployment, traffic splitting, etc. While the kn CLI provides strong operational control, a visual interface is beneficial for many Kubernetes users.
The knative plugin for headlamp fills this very gap by providing an intuitive visual interface for managing Knative resources like Kservice, Revisions and Networking.

This allows users to Add/Edit Kservice, View Revisions, Manage traffic splitting between revisions, Autoscaling configuration and Shows Network Details

KService

A Knative Service (KService) is the top-level resource that manages the entire lifecycle of your serverless workload. It automatically provisions the underlying routes, configurations, and revisions needed to get your application running and exposed to traffic.

Since many fields may require frequent changes, we have added a toggle switch to switch between Read and Edit mode.

Traffic Splitting
Traffic splitting between all revisions are shown along with their tags which redirect to their respective URL

Autoscaling Configuration
Autoscaling features like Target Utilization %, Container Concurrency, Activation Scale, etc.

Revisions

A Revision is a point-in-time, immutable snapshot of your code and configuration. Every time you update a KService, Knative automatically generates a new Revision. This makes it incredibly easy to roll back to previous versions or run multiple versions simultaneously for A/B testing.

The Revision view surfaces information like incoming traffic, tags, parent service, concurrency control, etc.

It also provides detailed information about each container, displaying the associated image, exposed ports, and environment variables.

Networking

A clear overview of the ingress settings.

[kahirokunn]

Thanks for writing this up! Great overview of the plugin's features.

One small suggestion: the phrase "providing a visual interface for the kn CLI" might give the impression that this plugin is a GUI wrapper for the kn CLI, which could lead users who don't use the kn CLI to think this plugin isn't relevant to them.

Since this plugin manages Knative resources directly, could we rephrase this to avoid implying a dependency on the kn CLI? For example, something like "providing an intuitive visual interface for managing Knative resources" would be more accurate and inclusive.

Thanks!