Before creating a feature request, please search existing feature requests to see if you find a similar one. If there is a similar feature request please up-vote it and/or add your comments to it instead

Why do you want this feature?
When draining nodes on a production cluster, it might be safer to use a health check between node/nodegroup draining loops - to ensure that until now things

Describe the solution you'd like
It would be neat to see the start time of plugins when looking at sonobuoy status. For example, when E2E are running, they may take a while, but when did they start?

$ sonobuoy status                                                                                                            
PLUGIN		STATUS		COUNT
e2e		running		1
systemd_logs	comple

PR o'clock

Description

Add cluster_create_security_group condition to create the security group rule named cluster_private_access

Resolves #980
Resolves #942

Checklist

• CI tests are passing

it seems that some configuration providers (eg https://github.com/cloudfoundry/cf-for-k8s/blob/master/supported_k8s_versions.yml) will benefit from ability to specify min/max version of supported k8s. we should also provide a way to bypass this check for users that do not care about it.

apiVersion: kapp.k14s.io/v1alpha1
kind: Config
minimumRequiredVersion: 1.26.0 # kapp binary versio

Works in Safari, Chrome for Mac, Chrome for PC, Edge, but not IE version 11.192.16299.0 on Windows 10

Would the maintainers consider making @io_bazel_rules_k8s//toolchains/kubectl:toolchain_type

visibility = ["//visibility:public"],

I'd like to create my toolchain targets in my own Bazel packages that depend on `@io_bazel_rules_k8s//toolchains/kubectl:toolchain_ty

There's a ssh_config fixture to simplify things a bit:

def given_check_pod_status(ssh_config, host, k8s_client, label, expected_status):

Originally posted by @gdemonet in scality/metalk8s#2369