There was two of them, right?
Yeah, yeah, so we got three of them, uh,
one of them, right?
Yeah, I think, yes, okay.
So yeah, I'm going to do a talk on IPv6.
That's just the people are coming coming in here.
And IPv6, I'm Kubernetes.
Let's get started.
So that's all who am I.
I'm from North Norway.
I work as a platform engineer that's up.
That's all those things.
I'll take a little first call and come out in norming.
I have all the CNC certifications, a lot of them.
Yeah, I'm using IPv6 at home since like 2013.
So I know how my own SNL.
Yeah, kind of for nerd.
So let's first talk about IPv4 or the legacy IP.
It's basically a corner that we're in protocol today.
It was standardized in like 19 then.
The eighties, it's been around for a while.
Most of you are probably pretty familiar with it.
You know, pretty standard IP of like the SML and 32 bits.
The biggest issue with like before today is it's ice.
There are four, three billion others as well.
And as you can last and the current wall population,
we just like, yeah, a lot, a lot more people.
And most people also have multiple devices and so yeah.
And the work going for that is today is we come for something called not.
It's basically like way to hide multiple users behind the same IP.
This brings a lot of complexity, a lot of limitations.
And it's not really a little bit of work, but it's kind of back
that it had to do because of the outcome of IP addresses.
So we're starting with IPv6 now.
For providers like the red, the red, the red, the 32,
started charging for the big IP for addresses.
More and more ISP and I was just starting to record care
right now, especially means that we have multiple layers of not.
It's even more complexity, so it brings a lot of issues as well.
And if you're having a lot of them, the users
bind the same external IP.
And also have things like services that are red, red limits,
like the Docker with IR, we have hospitals for IPv4 address,
if you don't authenticate.
So it's going to be interesting.
You have all the users behind the same external IPv4 address.
And yeah, they also if you want to get them out of the day,
this is the repo, if you want to get them out of here.
The queue is like 500 days plus sort of time.
You can see it's growing and growing.
Growing, so basically, we are out of IPv4,
public addresses.
We have to buy it to film something today.
And it's quite expensive.
So the fix is basically IPv6.
It was implemented in the first draft,
it was in 1998, so it's for something new,
new, actually.
There are a lot of new things about IPv6,
but the biggest one and the most important one is the larger address space.
So I have 120 bits, because if you don't know,
basically, the bitmap knows that that's a lot of larger.
So this is the number of IPv4 address for three billion around.
This is the number of people in the world currently,
at least my last day, Google said so.
So pocket-pocket metric, and this is the number of IPv6 addresses.
It's quite a lot larger, and that's something
going to run out of anything soon, and who can probably sustain us a lot of
years into the future.
And that's going to try to pronounce the number, but it's a lot of larger.
Also, some visitors say, significantly,
when this is in the space, it's not like this time.
It's a lot of data that I've before, and I've just
huge circle of being IPv6 address.
So it's quite a lot bigger address space.
So yeah, it's based on hack-fax,
there's a lot of the annotations are going to do
into the details here, how to do it, but it's
yeah, some of you have probably seen an IPv6 address.
There's basically no need for not to extend their address space.
There's still some can be so not here and there, but at least
but extending the space, there's basically no need.
This is the stats from Google from yesterday, I think.
They're close to 50% adoption.
So under users are slowly getting there.
It's a list in the last five years that we've not got 20%
increased, so hopefully it will continue at that speed, at least for a while.
So we're like, then under users are getting there.
And also bedroom is likely a 71% this is quite good above average.
So the issue is, I'm on a vision site,
lots of talking, lots of innovations, websites.
Like, on a vision banking is like 19% support IPv6.
I think this is just the front page.
It was just like the very basic IPv6 support.
So now even IPv6, I think it's like 25% major website
or the six public services, 50%.
But if you also take into account that there's actually a lot of
say that public services needs to be IPv6 already.
If the option is kind of that, if there's a lot that says that you have to do it.
And like the biggest one, if you are the developer,
it's like, it doesn't still support IPv6.
And this is kind of sad for shame on all of them.
This basically means that you need to run dual stack.
You need to support both IPv6 and IPv4 for a while.
So if I have something called dual stack,
means that for an both, you don't want to have an IPv4 on IPv6 address.
And we can use it either.
So if it depends depending on what your destination is,
just the destination is, you can use IPv4 or IPv6.
But this means that you need to have a DNS record for all the services you want to use in both.
More than operating systems prefer IPv6 or IPv4, but it's not guaranteed.
Sometimes it is preferred to use IPv4 even if you have an IPv6 connection.
And that's a lot of complexity.
It's usually not certainly had two stacks.
You need to secure both of them.
You need to think about security products and however we use
and everything for both of the stacks.
And for other things, you might end up with some traffic on IPv4 and IPv6 and yeah.
It's more complex.
For clients, this is mostly still needed.
Unless you have something called IPv6 mode,
it is actually an in-use on the Wi-Fi here.
So if you have an iPhone, you can actually see that you don't get the superware IPv4 address.
And there are a few people who only get the public IPv6 address here on your iPhone with this supercure.
For services, it's supposed to undo service.
This is still needed since it's only around 50% support IPv6.
And the service that mostly talked each other,
then why do you need both stacks if you have a database server,
it's supposed to talk to the back-and-series.
But the value of the database server needs to have up before on IPv6.
There's little need for it.
So getting into Kubernetes,
at V6 only Kubernetes has been supported for OI.
It's basically means that the pod-runner service
on an IPv6 address,
do you stack with the implement on the Wi-Fi there in Kubernetes 1.23,
which means that every pod begots an IP from each family.
So we have basically a dual stack, so as we mentioned,
and then communicate the service as can be declared as a single or dual stack support for them.
And now we also means that each pod have an IPv6 address,
can be a public IPv6 address.
That means that it's basically still needed to think about the curators since it's
public IPv6 address, but there's no need for not.
So you can basically have an end-to-end connectivity behind the pod,
then do an user for the service.
This talk is mostly about how running your own method setups,
but the mention of, like, the mention of the support units in the cloud providers,
like Amazon, yes, the support dual stack for OIL,
and it's a beast support dual stack,
and as sure support dual stack with kind of them,
we are nothing in the way it's in there.
And there's, like, mixed method in the providers,
and not everything is supported always,
and you can find bugs that are supported,
that's the existing IPv4, and there's still some issues,
but that is, that is, you sort of do support it.
So yeah, a mention of public prefix.
You're going to also know, IPv6 on a private prefix,
can I basically have the same as we have in IPv4,
and RFC-1918, that means that you need some sort of
not those some sort of proxy or something,
to, like, outside of your network,
but it brings a lot of going into the details.
To talk public prefix, basically,
you need to get the public prefix from your ISP, your private provider,
or some sort of, have a prefix, or a locator to you.
And then we divide that prefix up into multiple smaller prefix x,
and then we will allow the locator to configure it in the Kubernetes.
And then we need to route subnet to the nodes using BGP,
most of the CNI support it.
And there's a error, because I'm going to issue the security open by default.
So if you just deploy a coupon cluster with a public app,
with six prefix x, and we have no fervor between all the ports
have direct connectivity to internet portways.
So you can, I have someone from the internet
talk to a port without anything between them.
So you need to have some fervores or something between there as well.
We've got a private prefix.
I mentioned here, we sort of, as well, isolated clusters between,
that we don't need to have some BGP supports.
If I have a home lab, it can be difficult to have BGP support
on a home router perhaps, so you can do run a private prefix.
It can use the disk use of the uniquely local addresses,
like everything I've done it to not be before.
But that means that we need to use not, or process,
or something like that, so it's their own access.
So then they will do the stuck in Kubernetes.
This is not just on the different components,
they can plug cube on the deploy cluster.
Yes, they find prefixes to the APS server and controller and proxy.
And it should be supported underneath CNI support.
And CNI is just standard for how container networking in Kubernetes works.
So they find software to get an IP address and connectivity.
Also, we see what IPv6 features are available.
I'm using CNI, with EBP support, or based on EBP F.
The support IPv6 only and the stack clusters,
the new IPv6 are load balancing, provide.
So I have a tool called Hubbell that provide flow of visibility,
so you can see IPv6 traffic are going in in internally and outside of it, cluster.
So I'm doing stack monitor services.
You can basically as mentioned, we can basically define newompos servers to be
single stack, or pure stack.
CNI can't go into the details, so that's all.
So yeah, and as you talk, perhaps,
it's IPv6 only.
I've been running it for all islands from the cluster,
and it works if it removes IPv4 at all.
It's quite good.
Removing nothing, if you're on a public prefix,
so that it's already about anything there.
Each port gets a globally unique IP,
so if you have a lack of input clusters,
you can pair them without any worries that the IDRs and IP overlap.
And we have an connectivity that's out and it's translation layers.
So IPv6 services, enabling it in Selium is just something that
exists in enable to true, when I before enable to pause.
And you set the IPv6 under the multiple IPv6 and you can get started.
It's simple as that.
I have a small, I can install it using KKS and Selium.
I don't have to publish the slides after all, so we can get it in there.
This is basically using nothing on that IPv6.
You can run it on laptop or it can have a small VM,
without any worries.
Kind of small, I guess, but you can see that each port here has some IPv6 address on
or the services system of the six address.
Then talking to IPv6,
before only there is this, as we mentioned, like services like GitHub,
doesn't support IPv6.
So you feel like you're just going to talk to things like GitHub.
You need to have some sort of layer between.
It can be a bad proxy like screen, or it can be a register like hardware,
that can be put to the cache, or it can be something called a 6-4.
This is better, nothing can trigger.
It got pretty complete, but at least,
and that basically means that you can have a client on IPv6 only talk to IPv4 services.
Doing it in production, like I've been like the small startup,
where there was like to do it and everyone is happy,
we have a larger enterprise, so there's a lot of the first,
and getting the first of all in a session of work can be a lot of the work,
because people are preferring to see other IPv4.
They don't let it down, they don't like it.
For them, it's new and complex, and they don't see the mini-meat for it,
especially large, and enterprises have a big pool of IPv4,
or the first, like they don't see the needle at all.
Many apps and libraries use a Zoom scenario before address,
so it's like, it crashes when it starts up because it doesn't find them up before address,
kind of, come in to see, and then it services,
especially in the cloud providers, like some of them own a support IPv4,
so you can stack again, and a lot of tooling like behind an IPv6 support
it won't support IPv4, and there's a lot of issues like that.
So yeah, we thought, I don't think I'm done,
if there's any questions, I have a few minutes left, I think.
Anyone?
Thank you.
You shared on a previous slide that you suggested using a slash 60,
prefix, and then that would allow you to have 16 apps with the next sample,
but yeah, okay, my question is going to be, how would you feel,
and don't shoot me for asking, if you use something small,
slash 64 for a node, if you've got one service running,
I don't think it's going to be any issue.
I'd go for something with the Docker documentation,
you used to say, use a slash 86.
Yeah, the IPv6 support kind of won't
support the network, go smaller on a slash 64,
that's like, so I love this a lot of this discussion around it,
doesn't mention also on a slash 64, it's mostly seen as like one public,
I prefer a rest in terms of like things like a writing,
limiting, and that's one of the things.
There's also done if it's having something to hold,
but you can go smaller, there's no issues, you can go smaller.
Another example is also, say, that you should go smaller,
this is just the way I deployed a cluster error, but yeah.
And a slash 60, like my seems like a lot of IP addresses,
if you have like a slash 29 as an enterprise,
you have like billions of like six or six this.
So you can go way, way, way, be your experience without the
and not using it in your network address space.
Don't know where they're.
So thank you for your thought.
A very naive question, maybe.
Although I do like IP version 4, I prefer it to IP version,
sorry, IP version 6, before IP version 4.
And normally if you have operating Kubernetes class,
you put a low balance and front of it.
So you normally not directly accessing the notes or the pots.
So besides being modern, what is actually the benefits?
Because in for IP version 4, I still have,
I still have like with a tens slash 8, I have an alpha IP addresses for my pots,
and to be honest, there's like there's no,
we shouldn't go and change all the clusters, that is only it today.
And you just like I mentioned, I just want to complex it in.
So running the stack clusters might not be benefit for because they're
basically none.
And I didn't mention like how do we get sounds in the cluster,
because there's no low balance or support boats at an or CBN,
that is from the support posts, both stacks.
But all of the benefits I've seen, if I did have to cluster,
and I have bring two clusters together.
And they were running the same IP space.
That really fixed the learning.
And IP-6 cluster, mostly, if for an at least different public,
you are guaranteed that you put this in it.
So for example, if you do a wire god mash,
we see a bit between two Kubernetes addresses,
you don't have the issue of de-caching IP range,
which is depending on yes.
Yes.
Okay, okay, this is something I understand.
Okay, and there you also have the benefit,
you don't have not on these two IP-6 other services.
But yeah, we can do one more question real quick,
but can the next speaker please show up at the front?
Thank you, and so two quick questions.
One of them, so you talked about the routing for
Delicate while showing the prefix at the pods.
Have you investigated whether you can use the HPV6PD
to automate that so you don't have to fath with manually setting routes?
I haven't invested enough, but on the various new thing being,
if they go to get the payload or within the nodes,
so if I notice I'll start with this year,
and all of them are advertising your prefix,
but they haven't invested enough so using the HPV6PD on this.
I don't know.
And the other one was you made mentioned,
met six, six, why when it shouldn't be used at all?
If you're there, it's like, because you have to route the prefix
into nodes somehow, using something like,
using each HPV, and then if you don't have that support,
it's like on your new laptop, you don't have to run,
just don't know if it's there, we have a public prefix on your own.
So using them directly, not six, six.
Yeah, I guess.
Sorry for the rush, thank you very much everyone.
Thank you.