検索
返信元:
It's the Monday back from Germany and I'm upgrading #Rancher #Kubernetes clusters. So far so good!
Got through a bunch of stuff without incident until Elemental and a Dell got in a fight and grub2 lost. Interesting that the gigabyte machines in the same cluster didn't have any issue with the same upgrade.
#Rancher
It's the Monday back from Germany and I'm upgrading #Rancher #Kubernetes clusters. So far so good!
My workshop is today on deploying #Nextcloud in #SUSE #Rancher Harvester at 4:45pm, Berlin time.
If you are curious about how to run nextcloud on #Kubernetes without knowing Kubernetes and without hacking any yaml to do it, then I look forward to seeing you this afternoon.
返信元:
One step closer to having our #Jenkins be fully #Kubernetes at work. It's not like it was particularly difficult to set up, but more that there was enough bare metal resources allocated to the CI that it was a backlog item. Moving to k8s workers means those bare metal worker nodes can become k8s workers and be available for other workloads and devs can have more flexibility in directly defining their build environment requirements.
Deployed a #Rancher #k3s cluster with #Harvester, added a project/namespace for Jenkins, generated the kubeconfig with Rancher Manager, and then added it as a cloud provider in Jenkins. It was that easy. I made a basic pod template that runs a #Fedora image in the GUI, then created a Jenkinsfile in a #forgejo #git repo that did 6 parallel tasks. #Jenkins picked it up and it was fun to watch k8s pull the Fedora images and do it's thing from there.
I'm thrilled to announce that I will be at speaker at the upcoming #NextcloudConf24 in Berlin next month!
I will be giving a workshop on running #NextCloud on #SUSE #Rancher #Harvester during the Community Conference portion (14th and 15th).
https://nextcloud.com/blog/nextcloud-conference-2024/
@[email protected]
返信元:
Having a weird hankering to run #FreeBSD again and I'm not sure why. I have no practical reason to do it, but there's something about it I miss. I'm definitely not in a place in life where I would consider running it as my main OS anymore like I did a little over a decade ago.
Welp, I got #FreeBSD 14.1 running in #Rancher #Harvester using the Cloud Init image, which unfortunately doesn't appear to play well with Harvester Cloud Init templates, nor with the format here:
https://community.ops.io/jmarhee/preparing-a-freebsd-cloud-image-with-cloud-init-22lh
But I was still able to log in via Harvester's VNC and configure ssh from there. Next step is seeing if I can somehow get qemu guest agent to run on it.
But I was still able to log in via Harvester's VNC and configure ssh from there. Next step is seeing if I can somehow get qemu guest agent to run on it.
Finally got #Ceph RBD reliably working in #Rancher #Harvester VMs. Volumes, snapshots, backups, migrations, etc. are all working now against an external Ceph cluster alongside the native Longhorn.
Looks like #Rancher 2.8 has graduated to stable as of 2.8.1!
https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-8-1/
#kubernetes
Using #Rancher #Fleet to make sure cert-manager is up to date and ready to go across several #Kubernetes clusters via #gitops. Sort of like ArgoCD at cross-cluster scale, and the helm stuff remains helm stuff when it's all said and done.
返信元:
@[email protected] For some reason, this reminds me that I have been wanting to give @[email protected] another go. It was my distribution of choice for about 8 years. The only reason I left was because the company I work for is so Ubuntu centric.
@[email protected] @[email protected] Well, #Rancher now owned by #SUSE, so that tracks! But I've ran #k3s on #CentOSStream and #AlmaLinux successfully as well. I think I've only deployed #RKE2 on SUSE variants (SLE Micro, Elemental OS, OpenSUSE Leap Transactional Server).
I think I've finally tamed this #OpenSearch setup on this #Rancher #RKE2 cluster. Today's adventure was schema conflicts. Pods labeled with "app" while others are labeled with app.kubernetes.io cause a problem for inputs as it looks to OpenSearch like there's a string where an object should be and the flatten hashes on the fluentd output wasn't quite enough to cut it, but the dedot filter brought it in the rest of the way there.
Just closed 176 tabs in #Firefox. The upside is I have #Rancher and #OpenSearch playing well together at the moment. 🥳 :apartyblobcat: 🎉
Yesterday, I deployed a #Rancher #RKE2 #Kubernetes cluster with #Cilium and removed kube-proxy in the process. Maybe I'm behind the times, but it's the first time I've done cilium (used to flannel, calico, canal, etc.). Looking forward to a simpler and faster Kubernetes!