Canonical today announced full enterprise support for Kubernetes 1.18, with support covering Charmed Kubernetes, MicroK8s and kubeadm. Committed to releasing in tandem with upstream Kubernetes, enterprises can benefit from the latest additions to enhance their day to day operations.
Today, we are excited to announce a huge step forward for Sysdig Monitor. We’re introducing the ability for our customers to use Sysdig to scale Prometheus monitoring to millions of metrics with long-term retention. The improvements we are releasing make Sysdig the first cloud-scale monitoring offering to deliver full Prometheus compatibility.
PromCat, short for Prometheus Catalog, is a resource catalog for enterprise-class Prometheus monitoring. Prometheus has been revolutionary in the way we monitor our cloud-native environments, attracting immense attention from the open-source community and making the amount of Prometheus monitoring resources explode. Now, there are so many resources available that it’s no longer easy to filter out the good ones and discard those that are poorly documented or obsolete.
Longhorn is cloud-native distributed block storage for Kubernetes that is easy to deploy and upgrade, 100 percent open source and persistent. Longhorn’s built-in incremental snapshot and backup features keep volume data safe, while its intuitive UI makes scheduling backups of persistent volumes easy to manage. Using Longhorn, you get maximum granularity and control, and can easily create a disaster recovery volume in another Kubernetes cluster and fail over to it in the event of an emergency.
In today’s era of microservices, containers, and containerized applications, software architecture is more complex. Kubernetes is king in this environment, orchestrating an army of Docker containers in more distributed environments.
AWS EKS has been supporting Linux containers for a while. However, without Windows container support some of the hybrid applications were not supported end to end. In addition, with the version of 1.14 of Kubernetes, AWS introduced Windows container support and with this feature, you would be able to run Linux and Windows containers in the same Kubernetes cluster namespaces thus enabling your hybrid applications to work on Kubernetes.
Kubernetes 1.18 is about to be released! After the small release that was 1.17, 1.18 comes strong and packed with novelties. Where do we begin? There are new features, like the OIDC discovery for the API server and the increased support for Windows nodes, that will have a big impact on the community. We are also happy to see how some features that have been on Alpha state for too long are now being reconsidered and prepared for the spotlight, like Ingress or the API Server Network Proxy.
If you’re an advanced Kubernetes user, you’ll likely want to configure parameters for specific use cases. While with Kublr, the most flexible Kubernetes platform on the market, literally everything is customizable (except, of course, if you want to replace Kubernetes with a different container orchestrator), a lot of the customization in the previous versions was still done via command line.
It was a cloudy winter morning when I had arrived at the office and found, to our horror, that a Kubernetes cluster was suffering from extremely high CPU and network usage and had become almost completely non-functional. To make things worse, restarting the nodes (the go-to DevOp solution), seemed to have absolutely no effect on the issue. Something was poisoning the network and we had to find out what it was and fast.
Identity and access management (IAM) in AWS is a way to grant access to AWS services and collect and transmit data and credentials. Most Kubernetes “Quick Start” guides for AWS do not adequately cover how to manage IAM access in your pods. This blog series will first go over the security issues specific to AWS IAM on Kubernetes, then compare solutions, and then we will end with a detailed walkthrough for setting up your cluster with one of those solutions.
