These are internal labels that are managed by the operator and cannot be removed. The operator will recreate them if they have been removed as it is watching these secrets for changes.
The credentials label is used to identify resources holding credentials and is a "user facing" label if you will. It can be used to rotate credentials if necessary.
You could temporarily exclude the cluster where you are trying to set the password from being managed by the operator.
However, this is a bit hacky in my opinion. If you just want a user with a set password the recommended way would be to just create a new user in the so called native realm via Kibana with the right permissions and password of your choice.
For that case ECK has extra support for the so called file realm where you would declaratively set up your users in a secret that is managed and controlled by you (see my link) as opposed to trying to manipulate the secret of the built-in elastic super user. The elastic super user should not be used in day-to-day operations anyway and is more meant as an escape hatch for admins if things go wrong (or for experimentation in a POC etc)
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.