Redhat has an infinite value for ulimit by default which kubernetes inherits via the container service being used, this can result in some pods maxing out cpu and memory (such as haproxy and rabbitmq). For containerd the following fix solved the issue:
# sed -i 's/LimitNOFILE=infinity/LimitNOFILE=65535/' /usr/lib/systemd/system/containerd.service
# systemctl daemon-reload
# systemctl restart containerd
# k delete deployment <asdf>
Thinking about redeploying my homelab from scratch, perhaps switching from xenserver back to vmware. I’d like to start out with external-secrets and have all secrets in a vault right from the beginning, also curious what a 100% open source, 100% kubernetes environment would look like. Maybe two networks, one 100% kubernetes, and a 2nd for windows client systems. Here’s the k8s plan so far:
k-seed:
- manual setup of seed cluster
- helm install argocd
- argocd install clusterapi/crossplane/etc...
- seed-argocd deploy non-production cluster using vcluster or clusterapi/crossplane/etc...
- deploy metallb & configure loadbalancer ip range (can we automate this w/ cluster deploy?)
- add cluster to seed-argocd instance
- seed-argocd deploy production cluster using vcluster or clusterapi/crossplane/etc...
- deploy metallb & configure loadbalancer ip range (can we automate this w/ cluster deploy?)
- add cluster to seed-argocd instance
- seed-argocd deploy argocd to production cluster (k-prod)
k-prod:
- argocd configure storageclass
- argocd deploy hashicorp vault
- configure as certificate authority
- configure as keyvault
- argocd deploy external-secrets
- configure to use keyvault
- add secret 'ca-bundle.crt': public certificate authority certificate in DER format
- *from now on all secrets to get values via external-secrets
- argocd deploy cert-manager
- configure to use hashicorp vault as certificate authority
- argocd deploy pihole
- configure dns1 & dns2
- argocd deploy external-dns
- configure to use pihole as dns
- update with annotations to use external-dns & cert-manager:
- argocd
- vault
- pihole
- *from now on all ingress yaml to include annotations for external-dns & cert-manager
- recommended: have annotations from the beginning, at this point they will start working
- argocd deploy keycloak
- configure realm: create or import from backup
- add secret 'default_oidc_client_secret': secret part of oidc client/secret
- configure a user account (or configure federation via AD, openldap, etc...)
- deploy all other apps
- oidc client_secret should come from external-secrets in all apps configured with oidc
- this might require an init container for some apps
k-ceph:
- pvc storage for all clusters
- block storage can be used for vm disks (making for easy hotswap)
- upgrade to 2 10gb ports on each host system
wdc: (kubevirt in theory but think i'll stick w/ a vm)
- domain controller
- user management
- dhcp
- wds
- wsus using dev sqlserver & data stored on e drive
When you put in a feature request to add OIDC to your favorite project, feel free to include a link to this video.
Something similar to https://lunch.pink but specific for work, so running in a container with OIDC setup for coworkers. Coworker then could create a lunch event public or private, invite folks, folks could respond with interest and vote for their favorite restaurants, or just keep their same favorite restaurants from last time.
As a webapi could create integrations into Teams or a mobile app.
Could be a good excuse to write a controller and some custom resource definitions. Some initial ideas captured:
---
New-Restaurant
Add new restaurant to favorites list
Get-Restaurant
Get listing of preferred restaurants
Set-Restaurant
Enable/disable restaurant as favorite to include with voting
Remove-Restaurant
Remove restaurant from favorites list
---
New-Event
Create new event
-Description ""
-IsViewable <true>
-IsInviteOnly <false>
-Timeout <when_voting_ends, default 5 minutes>
Get-Event
Show all events if admin, otherwise only show public events, or events you've been invited to
Set-Event
Adjust attributes 'IsViewable', 'IsInviteOnly', and reopen voting.
Remove-Event
Remove event
---
New-Invite
Create new invitation to event
- only owner can create invitation
- invite id is a guid
-Username <username> // <optional> send through teams, or email, etc...
-EventId
Get-Invite
View current/expired invitations
Set-Invite
Accept / Reject an invitation
Remove-Invite
Withdrawl an inviteEvery now and then you come across a technology that you didn’t know about before, and you just can’t believe you haven’t been using the technology all this time.
Of course, at least you did find it … eventually. Thank goodness.
I find myself just shaking my head in almost disbelief at all the things this thing can do.
It’s interesting to see what countries your apps are connecting to, who is accessing your website, logs of access, etc… so much data to geek out about.