Chris Gaun and Max Werner from D2iQ write about expanding upon Kubernetes by using new distribution and Day-2-ifying practices.

Not much has changed about end users’ hybrid and multi-cloud strategy in 10 years. Now that Kubernetes is everywhere—GKE, EKS, OKE, AKS, DIY, Konvoy—it is time to expand upon the staid approach by deploying a distribution on top of and Day-2-ify-ing those existing Kubernetes clusters.

Step 1 of 7

14%

Which of the following best describes how you currently monitor and manage systems across your hybrid cloud environment?(Required)

Multiple separate tools for different environments

Multiple separate tools for different monitoring and management functions

Single consolidated dashboard

Custom built monitoring and management solution

No full monitoring and management solution

Don’t know

How valuable would it be for your monitoring and management solution to incorporate predictive analytics to help you identify and address system issues that are critical and not waste time or effort working through all the data and “noise” that is not critical?(Required)

Extremely valuable

Moderately valuable

Somewhat valuable

Slightly valuable

Not valuable

How do you most typically address potential system issues BEFORE they impact your operations?(Required)

Automated workflows and playbooks to remediate potential issues as soon as they are detected

An orchestrated response process that leverages automation, AI, and human expertise to rapidly respond to potential issues

Advanced monitoring tools such as predictive analytics and anomaly detection to proactively identify and address potential issues

Respond to issues as they arise, using manual processes and troubleshooting techniques

A combination of automated remediation, orchestrated response, and/or proactive monitoring to address potential system issues

Don’t know

Other

What methods does your organization use to control and monitor cloud/IT spending?(Required)

Centralized procurement processes

Pre-approved budget thresholds

Automated cost monitoring tools

Department-level spending controls

Regular cost audits and reviews

Cloud cost optimization platform

Approval workflows for resource provisioning

Native financial operations tools provided by the cloud provider

No formal controls in place

Don’t know

Other

Please specify:

Which methods do you rely on most to detect security vulnerabilities in your systems?(Required)

Automated scanning tools

Manual assessments

Vendor notifications

Threat modeling (for early detection)

None of these

Don’t know

Other

Please specify:

What are the TWO most common ways you prioritize vulnerabilities to address within your environment?(Required)

Based on potential impact

Based on exploitability

Regulatory compliance requirements

Based on CVSS scores

Risk-based analysis of multiple factors

First-in-first-out approach

No formal prioritization process

Don’t know

How do you typically handle system updates and security patches?(Required)

Automated updates and patches

Manually review and apply updates and patches on a regular schedule

A combination of automation and manual review

Apply updates and patches on an as-needed basis.

Outsourced update and patch management

No defined process

Don’t know

Other

Δ

The Kommander product strategy has always assumed that users will sometimes have existing Kubernetes clusters or have already decided on a particular vendor/provider. Kommander still delivers value to those customers. One way we planned to do that before even the first line of code was committed on any of our products was to take the Day 2 Kubernetes-based addons from Konvoy and federate them out to 3rd party clusters, making those clusters Konvoy-like and giving users the same operational view in Kommander no matter which managed cluster lies beneath. Over time, D2iQ will continue to expand our roster of  Day 2 addons and give operators more consistent capabilities on all their clusters.

Read the full blog post here:

https://d2iq.com/blog/hybrid-and-multi-cloud-is-tired-federated-distribution-is-wired