| 23 Jul 2021 |
 Alexey Murz Korepov | Seems there is also hostPath as alternative to local volumes, maybe even it will suit more for my needs... | 07:05:26 |
 cxz38 | try to avoid binding yourself into hostPath volumes, this way you couple yourself very tightly to the host machine. This is exactly why there is a decoupling of PVs and PVCs. I'm not sure what kubernetes distribution you've installed but k3s for example comes bundled with at local path provisioner (https://github.com/rancher/local-path-provisioner) that still uses the local disk but it will manage that lifecycle fr you. You can try that project to make it all a bit easier. | 07:14:30 |
| cxz38 | also read the k8s docs for volumes a least once! https://kubernetes.io/docs/concepts/storage/persistent-volumes/ | 07:14:58 |
| Alexey Murz Korepov | I already read it not only once, but understanding the whole logic is not so easy, from the docker side it looks overcomplicated to me... so this is why I asking stupid questions here :) sorry | 07:18:26 |
| Alexey Murz Korepov | In reply to @rio:rio.systems
try to avoid binding yourself into hostPath volumes, this way you couple yourself very tightly to the host machine. This is exactly why there is a decoupling of PVs and PVCs. I'm not sure what kubernetes distribution you've installed but k3s for example comes bundled with at local path provisioner (https://github.com/rancher/local-path-provisioner) that still uses the local disk but it will manage that lifecycle fr you. You can try that project to make it all a bit easier. I just install k8s on my Ubuntu system as packages from system repo, the "local-path-provisioner" seems good solution - will try to add it, thanks! | 07:19:09 |
| cxz38 | if you don't want to screw up your system while playing with all of this you can run k3s in docker using k3d (https://k3d.io/) or "normal" kubernetes in docker using kind (https://kind.sigs.k8s.io/). boots up in seconds and gets deleted in seconds as well. A lot easier than reinstalling your entire machine ;) | 07:21:01 |
| Alexey Murz Korepov | wow, launch docker containers inside k8s that already launched as docker - 🤯 | 07:25:03 |
| cxz38 | turtles all the way down | 07:28:12 |
| Alexey Murz Korepov | And one more question - where k8s is storing it's applied configuration (to backup it, or even simply lookup), after I launched kubectl apply -f myfile.yaml? In /etc/kubernetes/manifests and nearby I don't see any changes, and via google can't find this info too... | 08:23:22 |
| cxz38 | https://kubernetes.io/docs/concepts/overview/components/#etcd | 09:09:08 |
| cxz38 | usually its etcd, there are other storage backends depending on the kubernetes distribution that you use. k3s for example defaults to sqlite, but can also use etcd (I use etcd in HA mode on my RPI cluster for example). | 09:10:07 |
| Alexey Murz Korepov | Thanks, that is exactly what I tried to find! | 09:10:46 |
| Alexey Murz Korepov | * Thanks, that is exactly what I tried to find! | 09:10:58 |
| cxz38 | Also you should never interact with that datastore directly to do changes. All those changes should go through the api server. If you want to take backups, etcd has a great snapshot system. It's all there in the docs. | 09:12:12 |
|  frnimh joined the room. | 10:22:08 |
|  Phase left the room. | 19:01:35 |
| 24 Jul 2021 |
|  anthr76 joined the room. | 01:33:43 |
| 26 Jul 2021 |
|  @mildred593:matrix.org left the room. | 09:24:16 |
|  @etra:matrix.org left the room. | 12:56:33 |
 schemanic | Hello | 14:07:57 |
| schemanic | Does anyone know how to interact with feature gates in EKS? | 14:08:08 |
| schemanic | I've implemented Volume Snapshotting, but now I need to convert my existing PVs to use the EBS CSI driver, which can implement Volume Snapshotting | 14:09:00 |
| schemanic | apparently the process revolves around altering feature gates on kubelet and on the API server | 14:09:26 |
| anthr76 | I would assume managing a launch template? | 14:24:35 |
| schemanic | I'm afraid I don't follow. I'm not doing anything with a launch template - I'm trying to convert a persistent volume to use a new CSI driver | 14:25:43 |
| schemanic | I'm sortof new to this so I likely am working on an incomplete idea of what's involved. | 14:26:22 |
| schemanic | I presume that the programs that implement kubernetes within an EKS cluster are run by AWS and are thus inaccessible to me | 14:26:48 |
| schemanic | So I'm trying to simply see what AWS has set for the cluster I'm working with | 14:27:14 |
| schemanic | Can anyone help me understand this? I've been trying to find help for a week and nothing has clarified this, even the primary source on the migration process | 15:16:28 |
| cxz38 | Sorry, I don't have any experience with EKS. But in general I think it's safe to assume that you won't have access to control plane level configuration in any hosted kubernetes platform. | 15:32:38 |
