検索


---
apiVersion: v1alpha1
kind: NetworkRuleConfig
name: tailnet-management-kubeapi
portSelector:
  ports:
    - 6443 # kubernetes API
  protocol: tcp
ingress:
  - subnet: 0.0.0.0/0
  - subnet: ::/0
:thinkhappy:
返信 0 · Renote 0

返信元:

This is likely the last time I'll have those kind of numbers as workloads have been largely moved to baremetal on premise #Kubernetes systems over the past year. We basically bought the same hardware we were renting from Google and now run things at a fraction of the spend. The CapX to do it was less than one year of the OpX spend to not.
返信 0 · Renote 0
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.
返信 1 · Renote 0