Sebastien Dionne

had the same issue with ubuntu-20.04 with packer 1.5.6

```` root@test-pcl114:~/k8s-install/test# free -g total used free shared buff/cache available Mem: 31 2 10 0 17 28 Swap: 0 0 0 root@test-pcl114:~/k8s-install/test# ```` I think that config should be enough,...

I need to create something like that example too. I found the example into https://github.com/bokuweb/re-resizable/blob/65960a8d36a14393d49356adf85d471e6aeba77b/stories/multiple.stories.tsx

@OneCricketeer look like it doesn't work. The pod is still a CrashLoopBackOff We see this warning : **WARN The configuration 'topic.replication.factor' was supplied but isn't a known config. (org.apache.kafka.clients.producer.ProducerConfig)** ````...

ok. but the error return to this ```` [2021-04-07 17:40:33,830] INFO Wait to catch up until the offset at 3 (io.confluent.kafka.schemaregistry.storage.KafkaStore) [2021-04-07 17:40:34,328] INFO Joining schema registry with Kafka-based coordination...

it's wierd. if I use 3.. schema registry doesn't crash

I added more RAM, more CPU to schema registry and I still get this ```` [2021-04-08 13:54:14,750] INFO Kafka version: 6.1.0-ce (org.apache.kafka.common.utils.AppInfoParser) [2021-04-08 13:54:14,750] INFO Kafka commitId: 958ad0f3c7030f1c (org.apache.kafka.common.utils.AppInfoParser) [2021-04-08...

[clabot:check]

no troubleI forgot that one I'll do that.

@gAmUssA I updated the readme to reflect changes to Helm 3 and I updated Prometheus and Grafana link (stable/xx) repos are deprecated.