Just in case, because a lot of people don't know this... When a company lists job requirements they aren't really requirements. Don't skip a job because it says you need X years of Y but you only have X-1.

They're basically writing down a wish list. They don't expect to get it or necessarily even care that much about some of the points.

Also "X years of experience" isn't really asking for literal years. It's a proxy for skill. They mean "as good as the average person who has been doing this for X years". If you're really good at it and can demonstrate it, that's good enough.

yeah the lead lecturer on my data engineering masters once told us about a job posting he saw asking for 8 years of Hadoop experience, even though Hadoop had only been publicly available for 5 years at the time.

it's often HR / hiring managers throwing some numbers into a text document based on what they've heard is important for the role, not what you'll actually need for the job.

similarly, something like "has previous experience with kubernetes" doesn't usually translate to "knows absolutely everything there is to know about kubernetes". it means "you've used it at least once, ideally more, but can at least talk about when / how you used it / what problems it solved and could probably get up to speed on it fairly quickly when you join and/or in the time before you join" (kinda writing this last bit about an interesting job posting i saw that i've been talking myself down on and i really ought to be doing the opposite).