bertyah

This is a huge issue for me and stackstorm in my ORG. I'm disappointed to see that this is open since 2019. I suffer from the exact situation that @Kami...

I'm deploying this in AWS EKS right now and I get the same error while deploying. Kubernetes version: 1.21 EKS platform: eks.9 Helm: 3.8.0

`[authentication.k8s.io/v1/TokenReview authorization.k8s.io/v1/LocalSubjectAccessReview storage.k8s.io/v1/CSIDriver apps/v1 scheduling.k8s.io/v1beta1 node.k8s.io/v1 discovery.k8s.io/v1beta1 apps/v1/DaemonSet authorization.k8s.io/v1/SubjectAccessReview authorization.k8s.io/v1beta1/SelfSubjectAccessReview storage.k8s.io/v1/VolumeAttachment admissionregistration.k8s.io/v1beta1 node.k8s.io/v1beta1 v1/LimitRange networking.k8s.io/v1/Ingress rbac.authorization.k8s.io/v1beta1/ClusterRoleBinding v1 metrics.k8s.io/v1beta1 v1/PodProxyOptions authorization.k8s.io/v1beta1/LocalSubjectAccessReview autoscaling/v2beta1 rbac.authorization.k8s.io/v1/Role apiextensions.k8s.io/v1/CustomResourceDefinition rbac.authorization.k8s.io/v1beta1/Role v1/Namespace v1/PodAttachOptions v1/Service extensions/v1beta1/Ingress authorization.k8s.io/v1beta1/SelfSubjectRulesReview batch/v1/Job...

Just to clarify, I am using the chart from helm.stackstorm.com which I believe is 0.100.0 I am not cloning this repo.

@cognifloyd We have a docker container we use that has all the related utilities to work with k8. From there it's sort of a wrapper command tool that runs kubectl...

Also experiencing this issue on mongo 4.4 Seems like I ran an action with a large dataset or I ran it too many times? Not sure. I can filter different...