enhancements
kubernetes-json-schema
Our great sponsors
enhancements | kubernetes-json-schema | |
---|---|---|
57 | 4 | |
3,222 | 289 | |
1.4% | 0.3% | |
9.8 | 0.0 | |
7 days ago | 8 months ago | |
Go | ||
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
enhancements
-
Exploring cgroups v2 and MemoryQoS With EKS and Bottlerocket
0 is not the request we've defined. And that makes sense. Memory QoS has been in alpha since Kubernetes 1.22 (August 2021) and according to the KEP data was still in alpha as of 1.27.
-
Jenkins Agents On Kubernetes
Note: There's actually a Structured Authentication Config established via KEP-3331. It's in v1.28 as a feature flag gated option and removes the limitation of only having one OIDC provider. I may look into doing an article on it, but for now I'll deal with the issue in a manner that should work even with a bit older versions versions of Kubernetes.
-
Isint release cycle becoming a bit crazy with monthly releases and deprecations ?
Kubernetes supports a skew policy of n+2 between API server and kubelet. This means if your CP and DP are both on 1.20, you could upgrade your control plane twice (1.20 -> 1.21 -> 1.22) before you need to upgrade your data plane. And when it comes time to upgrade your data plane you can jump from 1.20 to 1.22 to minimize update churn. In the future, this skew will be opened to n+3 https://github.com/kubernetes/enhancements/tree/master/keps/sig-architecture/3935-oldest-node-newest-control-plane
-
Kubernetes SidecarContainers feature is merged
KEP: https://github.com/kubernetes/enhancements/tree/master/keps/...
TLDR: Introduce a restartPolicy field to init containers and use it to indicate that an init container is a sidecar container. Kubelet will start init containers with restartPolicy=Always in the order with other init containers, but instead of waiting for its completion, it will wait for the container startup completion.
So, until now, a sidecar container was just the idea of running helper containers in you Kubernetes pod that were 'helpers' for something: connection to databases or vpns, mesh networking, pulling secrets or config, debugging... But they didn't have special status, they were just regular containers in your pod.
This sometimes posed some problems because they weren't available for the full life cycle of the pod, notably on the init process. So if your init containers needed secrets, connections, networking... that was being provided via a sidecar container, you were going to have a hard time.
With this change, among other things, sidecars containers are going to be available for the whole life cycle of the pod.
There are other implications, probably, but I still haven't finished reading the KEP [0]. Check it out, and there you'll find its motivation and several interesting examples.
0: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/753-sidecar-containers
The KEP (Kubernetes Enhancement Proposal) is linked to in the PR [1]. From the summary:
> Sidecar containers are a new type of containers that start among the Init containers, run through the lifecycle of the Pod and don’t block pod termination. Kubelet makes a best effort to keep them alive and running while other containers are running.
[1] https://github.com/kubernetes/enhancements/tree/master/keps/...
-
When you learn the Sidecar Container KEP got dropped from the Kubernets release. Again.
full Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/753-sidecar-containers/README.md
-
Kubernetes 1.27 will be out next week! - Learn what's new and what's deprecated - Group volume snapshots - Pod resource updates - kubectl subcommands … And more!
If further interested, I may recommend checking out the KEP. I love how they document the decision making, and all these edge cases :).
- Twitter to un-verify people who don’t pay $8/month starting on April Fools’ Day
kubernetes-json-schema
-
WebAssembly: Docker Without Containers
Hey, so I thought I remembered your username. This isn’t the first interaction we’ve had, or I’ve seen you have, that follows this similar pattern. In fact it’s the third example from you under this post!
It’s not a particularly pleasant experience to discuss anything with you, as after you make a particularly vapid and usually ice-cold take that is rebuffed, you seem to just try to make snarky replies rather than engage.
Understand that if you post your takes here they may be discussed and challenged, and if you don’t want this then I would refrain from initially commenting.
In response to your comment: They do. All Kubernetes resources are typed with JSON-schema definitions. Because of course they are, how else would kubernetes validate anything. https://kubernetesjsonschema.dev/
Anyone who’s used k8s at all knows this, if only from the error messages. From this you get autocompletion and a wide ecosystem of gui configuration tools. I like lens (https://k8slens.dev/).
-
Data and System Visualization Tools That Will Boost Your Productivity
To avoid spending unreasonable amount of time trying to find that one wrong indent, I recommend you use schema validation and let your IDE do all the work. You can use validation schemas from https://schemastore.org/json or custom schemas such as these for Kubernetes to validate your files. These will work both with JetBrains products (e.g. Pycharm, IntelliJ) as well as VSCode (see this guide)
-
Test manifest compatibility against version
Seems like they haven't generated v1.20+ schema. It might work if you generate the schema yourself and feed it to KUBEVAL_SCHEMA_LOCATION
-
A Deep Dive Into Kubernetes Schema Validation
Kubeval - instrumenta/kubernetes-json-schema (last commit: 133f848 on April 29, 2020)
What are some alternatives?
kubeconform - A FAST Kubernetes manifests validator, with support for Custom Resources!
spark-operator - Kubernetes operator for managing the lifecycle of Apache Spark applications on Kubernetes.
klipper-lb - Embedded service load balancer in Klipper
Hey - HTTP load generator, ApacheBench (ab) replacement
kubeval - Validate your Kubernetes configuration files, supports multiple Kubernetes versions
connaisseur - An admission controller that integrates Container Image Signature Verification into a Kubernetes cluster
pixie - Instant Kubernetes-Native Application Observability
conftest - Write tests against structured configuration data using the Open Policy Agent Rego query language
kubernetes - Production-Grade Container Scheduling and Management
lakeFS - lakeFS - Data version control for your data lake | Git for data