K8s KEPs
They are not just feature proposal. It is about
- Feature Design
- Different Alternatives
- Testing plan
Feature LCM = Feature, Deprecation, update. Captured in KEP
What is KEP? KEP-0000 K8s Enhancements Proposals
A unit of work: combined features or single feature or major changes
Capture decisions in well crafted artifacts
KEP has YAML based metadata.
/enhancements/keps
Stages:
1. Alpha: Disable by default. Enable with Feature Gate
2. Beta: API groups disable by default. Feature is enable.
3. GA: All enables
Demo
Git Issue : 114465 Add Sleep for pod life cycle handler
Let sleep is first class citizen, so no need to add its binary.
KEP is not hard but time taking. We need to take sign in from different people of community.
Feature = Enhancement = KEP
Non-Goals are very important, so distraction is avoided
Proposal section of KEP has technical part. Then read the code
Then "Design Details" may have pseudo code
"Graduation Criteria" for all 3 stages.
"Upgrade / Downgrade strategy"
K8s repo has staging repository.
SCHEO
/hack/update-codegen.sh will generate auto code
We can have KIND image with our own k8s code using config.yaml for KIND Also enable Alpha feature flag
KubeAPI Server YAML
Look for post-release blogs for user-firendly docs. Mid-release blogs also.
Beta to GA then remove feature enable check
KEP also captures all PR
0 comments:
Post a Comment