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
then kubectl apply of the following SolrCloud config
# specs: https://apache.github.io/solr-operator/docs/solr-cloud/solr-cloud-crd.htmlapiVersion: solr.apache.org/v1beta1kind: SolrCloudmetadata:
name: search-clusterspec:
# change the date below to trigger a manual restartcustomSolrKubeOptions:
podOptions:
annotations:
manualrestart: "2025-02-06T07:57:00Z"replicas: 2solrJavaMem: -Xms512M -Xmx1GsolrImage:
tag: 9.8.0solrSecurity:
authenticationType: BasicdataStorage:
persistent:
reclaimPolicy: DeletepvcTemplate:
spec:
resources:
requests:
storage: 6GisolrAddressability:
podPort: 8983commonServicePort: 8983
as you can see, basic auth is supposed to be enabled, yet the cluster has no authentication.
I tried deleting the SolrCloud and recreating it multiple times ( also deleted all PVCs ), the security.json is always empty
The bootstrape security.json secret is created but it seems like its never used.
Here some debugging commands and their outputs, might help understand the issue:
kubectl describe solrcloud/search-cluster
Name: search-cluster
Namespace: default
Labels: <none>
Annotations: <none>
API Version: solr.apache.org/v1beta1
Kind: SolrCloud
Metadata:
Creation Timestamp: 2025-02-06T10:48:25Z
Finalizers:
storage.finalizers.solr.apache.org
Generation: 2
Resource Version: 38419295
UID: 3f94f03a-9d8c-4988-a991-a4fa225b0b8e
Spec:
Availability:
Pod Disruption Budget:
Enabled: true
Method: ClusterWide
Busy Box Image:
Repository: library/busybox
Tag: 1.28.0-glibc
Custom Solr Kube Options:
Pod Options:
Annotations:
Manualrestart: 2025-02-06T07:57:00Z
Default Init Container Resources:
Resources:
Data Storage:
Persistent:
Pvc Template:
Metadata:
Spec:
Resources:
Requests:
Storage: 6Gi
Reclaim Policy: Delete
Replicas: 2
Scaling:
Populate Pods On Scale Up: true
Vacate Pods On Scale Down: true
Solr Addressability:
Common Service Port: 8983
Pod Port: 8983
Solr Image:
Repository: library/solr
Tag: 9.8.0
Solr Java Mem: -Xms512M -Xmx1G
Solr Log Level: INFO
Solr Security:
Authentication Type: Basic
Update Strategy:
Managed:
Method: Managed
Zookeeper Ref:
Provided:
Admin Server Service:
Chroot: /
Client Service:
Config:
Headless Service:
Image:
Pull Policy: IfNotPresent
Repository: pravega/zookeeper
Max Unavailable Replicas: 1
Replicas: 3
Zookeeper Pod Policy:
Resources:
Status:
Internal Common Address: http://search-cluster-solrcloud-common.default:8983
Pod Selector: solr-cloud=search-cluster,technology=solr-cloud
Ready Replicas: 2
Replicas: 2
Solr Nodes:
Internal Address: http://search-cluster-solrcloud-0.search-cluster-solrcloud-headless.default:8983
Name: search-cluster-solrcloud-0
Node Name: gke-main-cluster-main-pool-0d3ce34b-nrmn
Ready: true
Scheduled For Deletion: false
Spec Up To Date: true
Version: 9.8.0
Internal Address: http://search-cluster-solrcloud-1.search-cluster-solrcloud-headless.default:8983
Name: search-cluster-solrcloud-1
Node Name: gke-main-cluster-main-pool-0d3ce34b-nrmn
Ready: true
Scheduled For Deletion: false
Spec Up To Date: true
Version: 9.8.0
Up To Date Nodes: 2
Version: 9.8.0
Zookeeper Connection Info:
Chroot: /
External Connection String: N/A
Internal Connection String: search-cluster-solrcloud-zookeeper-0.search-cluster-solrcloud-zookeeper-headless.default.svc.cluster.local:2181,search-cluster-solrcloud-zookeeper-1.search-cluster-solrcloud-zookeeper-headless.default.svc.cluster.local:2181,search-cluster-solrcloud-zookeeper-2.search-cluster-solrcloud-zookeeper-headless.default.svc.cluster.local:2181
Events: <none>
⭕️ UPDATE:
I deleted the SolrCloud, recreated it with Solr 8.11.4 and it worked, then deleted that, and created with 9.6.1 and it also worked.
So I deleted it again (without deleting the zookeeper PVCs) and recreated it with 9.8.0 and it worked.
Hey there, having the same problem here. I will add that version 9.7.0 works fine with a fresh new deploy too, so I'm guessing it's an issue related specifically with the 9.8.0 version.
I encountered the same issue with version 9.7.0 when creating my cluster from scratch with this version. However, upgrading from version 9.6.1 (with authentication already in place) to later versions works correctly.
Hi team,
I have a very simple setup and it can be easily replicated:
started by installing the operator on a fresh k8s cluster using a helm chart:
then
kubectl apply
of the following SolrCloud configas you can see, basic auth is supposed to be enabled, yet the cluster has no authentication.
I tried deleting the SolrCloud and recreating it multiple times ( also deleted all PVCs ), the security.json is always empty
The bootstrape security.json secret is created but it seems like its never used.
Here some debugging commands and their outputs, might help understand the issue:
The text was updated successfully, but these errors were encountered: