vishavjeet somwanshi

Further updating this parameter ```upgrade_acknowledgements_for = 4.13``` under resource ```rhcs_cluster_rosa_classic.rosa```. Initiated terraform apply and it went through. ``` resource "rhcs_cluster_rosa_classic" "rosa" { name = var.cluster_name cloud_region = var.aws_region aws_account_id =...

One question on this, suppose I have already cluster deployed and i introduce ```upgrade_acknowledgements_for = 4.13``` under resource rhcs_cluster_rosa_classic in terraform code, it gives below results when we run terraform...

We are good to close this issue.

@piyush-bhanushali1 I'm trying to deploy the keydb as a statefulset with 2 replica's and i want to deploy these two pods as active-active .. have you tried this scenario or...

I'm also seeing this error in `compactor` and `ingestor` pods in our TempoStack setup. Actually, i've 2 different TempoStack setup in 2 different Openshift cluster but i found this error...

Just for an update, i've updated the Tempo operator to the latest version `0.14.1-2 `. post upgrade i could see the options to setup the resource quota for each individual...

@joe-elliott It seems Currently, the custom resource has no specific parameters to modify these values directly. Checking the config file I have found the following: ``` FIELDS: extraConfig ExtraConfigSpec defines...

Now, i'm struggling with setting up below configuration under `querier`. ``` frontend_worker: grpc_client_config: max_recv_msg_size: 1.34217728e+08 max_send_msg_size: 1.34217728e+08 ```

This has been solved, Thanks!

Thanks @c-kruse I was able to deploy network observer successfully. I thought that deployment could be similar to the controller and we can deploy it under one namespace and scrape...