Nick Young
Staff Engineer at Isovalent
Sydney, Australia
Actions
Nick has been working to prevent the entropic downfall of systems for 25 years, across datacenters, clouds, networking, and others. He's a Staff Engineer at Isovalent, a committer on Cilium, and a maintainer on the Kubernetes Gateway API project, where he works on improving the ingress and mesh experiences. In his spare time, he spends time with his young family, then with whatever's left he keeps up with stereotypical nerd hobbies. Random fact: he took notes at university in the Tengwar, Tolkien's elvish script.
Badges
Area of Expertise
Gateway API: Beyond GA
The Gateway API project is the next generation of ingress (and service mesh) APIs for Kubernetes. The Gateway API project had it's GA release at the end of last year, but that really is just the beginning of the huge future ahead of the project.
In this talk we'll discuss what's going on in the project, and what are some of the next big features and what their status is. We'll have some specific feature focuses, including our "Conformance Profiles" project which enables conformance testing and reports which are an invaluable asset to the project, and can be very valuable to users as well.
If you have general Q&A about Gateway API this could be a great place to stop in and ask your questions.
Gateway API: The Most Collaborative API in Kubernetes History is GA
Gateway API has graduated to GA! In this session, we will share the journey it took to get here, highlighting the incredible story of what has likely been the most collaborative API development process in Kubernetes history, with over 150 contributors and 20 implementations already.
This API also represents a fundamental shift in how Kubernetes APIs are developed. Although this may be the first CRD-based Kubernetes API to graduate to GA, there are already others in progress. We’ll talk about what this means for the future of Kubernetes, and the ecosystem as a whole.
Finally, we’ll give an overview of the API, describing how it can be used for load balancing, in-cluster routing, and service mesh configuration. You’ll learn what it means for CRDs to be considered GA, and when, why, and how you can migrate to Gateway API if you’re not already using it.
Gateway API: What's new, what's next?
Gateway API represents the next generation of ingress and service mesh APIs for Kubernetes. Since its promotion to GA (General Availability) last year, numerous features have been added, with many more in development.
In this talk, we will introduce the latest enhancements, review all recent changes to the API, and discuss what lies ahead. Many features are planned to graduate to GA in the upcoming releases, while others will be introduced as experimental. This talk is the ideal opportunity to familiarize yourself with these changes, connect with the Gateway API community, and get answers to all your questions!
Still Don't Do What Charlie Don't Does - Making CRD changes safer
Many Kubernetes installations use controllers that include Custom Resource Definitions (CRDs) to extend their capabilities. However, because CRDs can only have one version installed in a cluster at any one time, version and change management can be very difficult.
This talk will benefit both controller implementers and users. For implementers, I have tips on how to more safely make API changes to their CRDs, and for CRD users, some tips on what to look out for when installing CRD updates. All of this is based on using experience from projects like Contour, Gateway API, and Cilium among others.
Learn things like:
Different CRD version management strategies - what’s worked and what hasn’t
How to make schema changes like pluralizing a field or changing field validation in a safe way
How not to make the same mistakes I did
Expect to come away from this talk having learned from my painful experiences handling CRD changes badly, but also having heard a bunch of Simpsons references.
Custom Resource Definitions: Let's talk about versioning and releases
Custom Resource Definitions (CRDs) in Kubernetes are a very powerful and useful bit of tech, but, as with any API, making changes safely can be a lot harder than it would seem.
At previous Kubernetes maintainer summits, we've talked about challenges for upstream CRD-based APIs, like Gateway API, Admin Network Policy and others, and what those projects are doing.
This talk is about discussing current pain points with versioning and releasing CRDs, and will include:
* a quick run through the requirements for making
safer API changes to CRDs
* some examples of versioning and release methods, and the problems that various projects have found
* Questions for future work and discussion
Come along to this talk if you're using CRDs in any capacity, in Kubernetes or other projects.
Don’t Do What Charlie Don’t Does - Avoiding Common CRD Design errors
Most controllers written for Kubernetes include their own Custom Resource Definition (CRD) - but it’s actually very easy to make mistakes in the CRD design that will cost a lot in longer-term maintenance.
Come and hear from Gateway API and Ingress controller maintainers about Charlie Don’t, the Kubernetes developer with the worst luck in designing CRDs, and how you can use his experience to avoid the most common problems with CRD design.
You should expect to come away from this session with an understanding of common CRD design errors and the ways you can avoid them.
Don't write controllers like Charlie Don't does: avoiding common Kubernetes controller mistakes
So you've learned about Custom Resource Definition (CRD) design errors, you've designed your CRD to avoid common mistakes, and now you're ready to write the controller.
Turns out there's a lot of gotchas in that process as well!
This talk explores the common pitfalls that the ever-unlucky Charlie Don't, who always makes the worst decisions, runs into when implementing a controller.
The talk should be particularly useful for anyone writing reconciliation loops that use Kubernetes objects, whether they are CRDs or not. You can expect to come away from this talk having learned about common mistakes like: straining the apiserver with too many status updates, missing updates in complex systems of CRDs, and having scaling problems from not using caching correctly.
No knowledge of the previous talks is required, so come and have a chuckle at poor old Charlie Don't's bad luck while picking up some tips for yourself.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top