Not create the StatefulSets when add the custom security.json in helm

[schotten]

Not create the StatefulSets when add the custom security.json in helm

[schotten]

@dan-niles ! Fantastic!!! Now, the problem is solved!!!

Only for informations (for other people who may have this problem), I:
1 - Create the solr-basic-auth

2 - Created the my security.json in the k8s

The user is necessary granted roles. In my case, i used the user "admin".

Again @dan-niles , tanks for your help!!!

[dan-niles]

@schotten Can you try adding another permission to security.json as follows...

{
  "name":"k8s-probe-1",
  "role":null,
  "collection":null,
  "path":"/admin/info/health"
}

I think the operator needs access to the /admin/info/health endpoint for readiness probes.

[schotten]

@dan-niles, i tryed your suggestion. Unfortunitly, the problem not solve. Even adding the rule in the security.json, the problem persist (not create the StatefulSets to Solr)

[dan-niles]

@schotten Maybe the password of your k8s-oper is not the same as the one in the secret. Can you try including basicAuthSecret in your helm config like this...

security:
  authenticationType: Basic
  basicAuthSecret: solr-basic-auth
  bootstrapSecurityJson:
    name: solr-security-roles
    key: security.json

First you will have to create a new Basic Authentication Secret called solr-basic-auth like this...

apiVersion: v1
kind: Secret
metadata:
  name: solr-basic-auth
type: kubernetes.io/basic-auth
stringData:
  username: k8s-oper
  password: some-password ### Change this 

Then replace the password for the k8s-oper in your security.json with the one you set in the above solr-basic-auth. You will have to encrypt the password, when you put it in security.json. You can do it with this Online Solr Password Encryption Tool.
After that, update your solr-security-roles with the new security.json.