-
Notifications
You must be signed in to change notification settings - Fork 15.1k
Closed
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.sig/architectureCategorizes an issue or PR as relevant to SIG Architecture.Categorizes an issue or PR as relevant to SIG Architecture.
Description
About
Kubernetes is a complex product and we would like to be able to better explain its core concepts through use of visuals. A visual language composed of symbols and icons will enable the creation of illustrative diagrams.
Current State
Only symbols we have today are in the first five slides of this Google Cloud Platform slide deck (if anyone has any others please share).
Proposal
- Prioritize concepts we want to have visualizations for.
- Discuss possible representations for concepts & post sketches. Loop in Google UX researchers for feedback.
- Establish basic visual guidelines for designs of different icons to adhere to as we expand the library. Symbols should be grounded in Material Design System Icons principles (e.g. "Bold, geometric, simple, intuitive, actionable, consistent"). The Slides of the Google Cloud Platform visual language should be referenced as inspiration, but we're also not going out of our way to align with this style.
- Design visually consistent vector (i.e. SVG) symbols.
Based on @bgrant0607's proposed concepts, I've put together the following list of concepts to consider for visualization:
- Pod
- All types of services:
- Cluster
- Nodeport
- Loadbalancer
- Headless
- Imported
- Ingress
- EndPoint
- Every controller:
- Replication Controller
- Replica Set
- Deployment
- DaemonSet
- PetSet
- Job
- ScheduledJob
- Rolling update
- Canary deployment pattern
- with ConfigMap
- Horizontal Pod Autoscaling
- ServiceAccount
- Secret
- Persistent Volumes and Persistent Volume Claims
- System Architecture
- Things we will need to diagram concepts and processes
- Virtual IP
- IP address
- Running Container
- Request / Response
As @pwittrock pointed out, we should focus first on designing visualizations for concepts, while keeping in mind how those visualizations will come together in more complex diagrams (e.g. deployment)
Reference
Vlaaaaaaad, tnir, sgandon, Jon007, joelhy and 1 more
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.sig/architectureCategorizes an issue or PR as relevant to SIG Architecture.Categorizes an issue or PR as relevant to SIG Architecture.