elvis-cai

same here if I set SCHEMA_REGISTRY_KAFKASTORE_TOPIC_REPLICATION_FACTOR to 3, The configuration 'topic.replication.factor' was supplied but isn't a known config. (org.apache.kafka.clients.consumer.ConsumerConfig) for 5.2.1

do we plan to support upgrade from cluster strimzi managed with zookeeper added to zookeeper-less mode using strimzi kafka operator in future release? (Background context: we are looking at migrating...

> @elvis-cai Please add some test cases to cover these changes. sure, doc & test added.

> Please fix the CI errors. my bad, last commit forget to update test code, updated

> Sorry for delay. Can you resolve the conflict? Then we run the test and merge this PR. Thanks! all good, conflict resolved and feel free to rerun the test,...

I am more looking forward to the feature https://github.com/apache/apisix-ingress-controller/issues/927, but sounds good to me , before that's implemented, will look at if I could fix the conflict and merge the...

+1, multi external url support with active health check and upstream node pass is the major block before we rollout Apisix ingress controller in all of our kubernetes clusters. It’s...

meet the same issue in 1.3.3/1.3.6 version, clusterpolicy for kube-system not work as expected.

``` │ Error: Provider produced inconsistent result after apply │ │ When applying changes to │ google_bigquery_dataset_iam_member.this["roles/bigquery.dataEditor │ user:[email protected] xxxxxx"], provider │ "provider[\"registry.terraform.io/hashicorp/google\"]" produced an │ unexpected new value: Root...

thanks @wakefun , tried with `NEXTAUTH_URL`, but unfortunately, still got the same result.