You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# export managed cluster kubeconfig:
kubectl get secret aws-${CLUSTER_NAME_SUFFIX}-kubeconfig -o=jsonpath={.data.value} | base64 -d > kubeconfig1
# get managed cluster pods:
KUBECONFIG="./kubeconfig1" kubectl get pod -A
Output (wall of Evicted and ContainerStatusUnknown pods, different namespaces), management services impacted:
Describe the bug
I managed to "paralyze" my aws managed cluster when testing "kubecost" deployment. Here is my setup and result:
To Reproduce
t3.medium
andaws-standalone-cp-0-1-0
):Install
kubecost
service template from k0rdent catalog.Create
MultiClusterService
:Output (wall of
Evicted
andContainerStatusUnknown
pods, different namespaces), management services impacted:Expected behavior
Only
kubecost
deployment has errors due to lack of resources. Sveltos agent is not impacted, kube-system pods are not impacted.Note: Tested with k0rdent 0.1.0 release
The text was updated successfully, but these errors were encountered: