Statements (58)
Predicate | Object |
---|---|
gptkbp:instance_of |
gptkb:Kubernetes
|
gptkbp:can |
Health checks
On specific nodes |
gptkbp:can_be_configured_for |
Using Helm values files
|
gptkbp:can_be_described |
Using kubectl describe command
|
gptkbp:can_be_listed |
Using kubectl get command
|
gptkbp:can_be_logged |
Using Fluentd
|
gptkbp:can_be_rolled_back |
To previous versions
|
gptkbp:can_be_used_to |
gptkb:Horizontal_Pod_Autoscaler
gptkb:Secrets Environment variables Custom resource definitions Network policies Taints and tolerations Config Maps Pod templates Service meshes Affinity rules Init containers Sidecar containers |
gptkbp:can_be_version_controlled |
In Git repositories
|
gptkbp:can_be_visualized |
Using Grafana
|
gptkbp:can_provide |
Resource limits
Pod disruption budgets Labels and selectors |
gptkbp:created_by |
kubectl command
|
gptkbp:deployment |
In multiple environments
|
https://www.w3.org/2000/01/rdf-schema#label |
Kubernetes Deployments
|
gptkbp:interrupts |
During updates
|
gptkbp:is_accessible_by |
Via service objects
|
gptkbp:is_defined_by |
Deployment YAML file
|
gptkbp:is_documented_in |
In Helm charts
|
gptkbp:is_integrated_with |
With CI/ CD pipelines
With monitoring tools |
gptkbp:is_managed_by |
Using Kubernetes operators
|
gptkbp:is_monitored_by |
gptkb:Kubernetes_Dashboard
For compliance For security compliance Using Prometheus |
gptkbp:is_optimized_for |
For performance
|
gptkbp:is_tested_for |
In staging environments
Using unit tests |
gptkbp:is_updated_by |
Using Git Ops practices
Without downtime |
gptkbp:latest_version |
Using annotations
|
gptkbp:provides |
Declarative updates
|
gptkbp:purpose |
Manage application deployment
|
gptkbp:replaces |
Using kubectl delete command
|
gptkbp:scales |
Manually or automatically
Up or down based on demand |
gptkbp:security |
Using RBAC
Using network policies |
gptkbp:supports |
Rollback functionality
Rolling updates Multiple replicas |
gptkbp:uses |
gptkb:Replica_Sets
|
gptkbp:bfsParent |
gptkb:Kubernetes
|
gptkbp:bfsLayer |
4
|