1_DevOps'ish

1_DevOps'ish

55093 bookmarks
Custom sorting
TACOS Framework
TACOS Framework
TACOS Framework has 6 repositories available. Follow their code on GitHub.
·github.com·
TACOS Framework
Steve Lord (@stevelord@bladerunner.social)
Steve Lord (@stevelord@bladerunner.social)
Attached: 1 image Hey @linuxfoundation@social.lfx.dev why are you sending takedowns on redbubble for generic Unix terms and project names you don't own?
·bladerunner.social·
Steve Lord (@stevelord@bladerunner.social)
The ABCs of Generative AI
The ABCs of Generative AI
Generative AI exploded onto the scene so quickly that many developers haven’t been able to catch up with new technical concepts in Generative AI. Whether you’re a builder without an AI/ML background, or you’re feeling like you’ve “missed the boat,” this glossary is for you!
·community.aws·
The ABCs of Generative AI
Blog: Kubernetes v1.28: Retroactive Default StorageClass move to GA
Blog: Kubernetes v1.28: Retroactive Default StorageClass move to GA
Author: Roman Bednář (Red Hat) Announcing graduation to General Availability (GA) - Retroactive Default StorageClass Assignment in Kubernetes v1.28! Kubernetes SIG Storage team is thrilled to announce that the "Retroactive Default StorageClass Assignment" feature, introduced as an alpha in Kubernetes v1.25, has now graduated to GA and is officially part of the Kubernetes v1.28 release. This enhancement brings a significant improvement to how default StorageClasses are assigned to PersistentVolumeClaims (PVCs). With this feature enabled, you no longer need to create a default StorageClass first and then a PVC to assign the class. Instead, any PVCs without a StorageClass assigned will now be retroactively updated to include the default StorageClass. This enhancement ensures that PVCs no longer get stuck in an unbound state, and storage provisioning works seamlessly, even when a default StorageClass is not defined at the time of PVC creation. What changed? The PersistentVolume (PV) controller has been modified to automatically assign a default StorageClass to any unbound PersistentVolumeClaim with the storageClassName not set. Additionally, the PersistentVolumeClaim admission validation mechanism within the API server has been adjusted to allow changing values from an unset state to an actual StorageClass name. How to use it? As this feature has graduated to GA, there's no need to enable a feature gate anymore. Simply make sure you are running Kubernetes v1.28 or later, and the feature will be available for use. For more details, read about default StorageClass assignment in the Kubernetes documentation. You can also read the previous blog post announcing beta graduation in v1.26. To provide feedback, join our Kubernetes Storage Special-Interest-Group (SIG) or participate in discussions on our public Slack channel .
·kubernetes.io·
Blog: Kubernetes v1.28: Retroactive Default StorageClass move to GA
Whoa!!! University of Chicago agrees to pay $13.5 million to students after being accused of participating in a 'price-fixing cartel' with other prestigious schools to limit financial aid
Whoa!!! University of Chicago agrees to pay $13.5 million to students after being accused of participating in a 'price-fixing cartel' with other prestigious schools to limit financial aid
After nearly two years of litigation, UChicago settled claims it conspired with top colleges including Brown and Yale to limit financial aid packages.
·businessinsider.com·
Whoa!!! University of Chicago agrees to pay $13.5 million to students after being accused of participating in a 'price-fixing cartel' with other prestigious schools to limit financial aid
HashiCorp's license change | LWN.net
HashiCorp's license change | LWN.net
Readers have been pointing us to HashiCorp's announcement that it is moving to its own "Business Source License" for some of its (formerly) open-source products. Like other companies (example) that have taken this path, HashiCorp is removing the freedom to use its products commercially in ways that it sees as competitive. This is, in a real sense, an old and tiresome story.
·lwn.net·
HashiCorp's license change | LWN.net
Blog: Kubernetes 1.28: Non-Graceful Node Shutdown Moves to GA
Blog: Kubernetes 1.28: Non-Graceful Node Shutdown Moves to GA
Authors: Xing Yang (VMware) and Ashutosh Kumar (Elastic) The Kubernetes Non-Graceful Node Shutdown feature is now GA in Kubernetes v1.28. It was introduced as alpha in Kubernetes v1.24, and promoted to beta in Kubernetes v1.26. This feature allows stateful workloads to restart on a different node if the original node is shutdown unexpectedly or ends up in a non-recoverable state such as the hardware failure or unresponsive OS. What is a Non-Graceful Node Shutdown In a Kubernetes cluster, a node can be shutdown in a planned graceful way or unexpectedly because of reasons such as power outage or something else external. A node shutdown could lead to workload failure if the node is not drained before the shutdown. A node shutdown can be either graceful or non-graceful. The Graceful Node Shutdown feature allows Kubelet to detect a node shutdown event, properly terminate the pods, and release resources, before the actual shutdown. When a node is shutdown but not detected by Kubelet's Node Shutdown Manager, this becomes a non-graceful node shutdown. Non-graceful node shutdown is usually not a problem for stateless apps, however, it is a problem for stateful apps. The stateful application cannot function properly if the pods are stuck on the shutdown node and are not restarting on a running node. In the case of a non-graceful node shutdown, you can manually add an out-of-service taint on the Node. kubectl taint nodes node-name node.kubernetes.io/out-of-service=nodeshutdown:NoExecute This taint triggers pods on the node to be forcefully deleted if there are no matching tolerations on the pods. Persistent volumes attached to the shutdown node will be detached, and new pods will be created successfully on a different running node. Note: Before applying the out-of-service taint, you must verify that a node is already in shutdown or power-off state (not in the middle of restarting). Once all the workload pods that are linked to the out-of-service node are moved to a new running node, and the shutdown node has been recovered, you should remove that taint on the affected node after the node is recovered. What’s new in stable With the promotion of the Non-Graceful Node Shutdown feature to stable, the feature gate NodeOutOfServiceVolumeDetach is locked to true on kube-controller-manager and cannot be disabled. Metrics force_delete_pods_total and force_delete_pod_errors_total in the Pod GC Controller are enhanced to account for all forceful pods deletion. A reason is added to the metric to indicate whether the pod is forcefully deleted because it is terminated, orphaned, terminating with the out-of-service taint, or terminating and unscheduled. A "reason" is also added to the metric attachdetach_controller_forced_detaches in the Attach Detach Controller to indicate whether the force detach is caused by the out-of-service taint or a timeout. What’s next? This feature requires a user to manually add a taint to the node to trigger workloads failover and remove the taint after the node is recovered. In the future, we plan to find ways to automatically detect and fence nodes that are shutdown/failed and automatically failover workloads to another node. How can I learn more? Check out additional documentation on this feature here . How to get involved? We offer a huge thank you to all the contributors who helped with design, implementation, and review of this feature and helped move it from alpha, beta, to stable: Michelle Au (msau42 ) Derek Carr (derekwaynecarr ) Danielle Endocrimes (endocrimes ) Baofa Fan (carlory ) Tim Hockin (thockin ) Ashutosh Kumar (sonasingh46 ) Hemant Kumar (gnufied ) Yuiko Mouri (YuikoTakada ) Mrunal Patel (mrunalp ) David Porter (bobbypage ) Yassine Tijani (yastij ) Jing Xu (jingxu97 ) Xing Yang (xing-yang ) This feature is a collaboration between SIG Storage and SIG Node. For those interested in getting involved with the design and development of any part of the Kubernetes Storage system, join the Kubernetes Storage Special Interest Group (SIG). For those interested in getting involved with the design and development of the components that support the controlled interactions between pods and host resources, join the Kubernetes Node SIG.
·kubernetes.io·
Blog: Kubernetes 1.28: Non-Graceful Node Shutdown Moves to GA
You're the OS! by drfreckles42
You're the OS! by drfreckles42
Become a computer operating system and try not to anger the user!
·drfreckles42.itch.io·
You're the OS! by drfreckles42
You don't hate JIRA, you hate your manager - Derek Jarvis' Blog
You don't hate JIRA, you hate your manager - Derek Jarvis' Blog
It seems like it has become popular to hate on JIRA. In fact, a good friend of mine sent me this, which is what triggered this post: (if you're the owner of the image, reach out to me and I'll attribute it properly) I'm usually…
·jarvispowered.com·
You don't hate JIRA, you hate your manager - Derek Jarvis' Blog