Setting default password via k8s secret.yaml not working

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The user tried to set a default password via k8s secret.yaml for Airbyte authentication but encountered an issue where the specified password was not used and a randomly generated one was used instead.


Question

I tried to set my own default password through k8s secret.yaml like <Authentication | Airbyte Documentation here>

secret.yaml:

kind: Secret
metadata:
  name: airbyte-auth-secrets
type: Opaque
stringData:
  instance-admin-password: "1234567"


  # Override these if you want to access the API with known credentials
  #instance-admin-client-id: # my-client-id
  #instance-admin-client-secret: # my-client-secret```
and `auth` section in `values.yaml`:
```# -- Auth configuration
  auth:
    # -- Whether auth is enabled
    enabled: true
    # -- Admin user configuration
    instanceAdmin:
      # -- Secret name where the instanceAdmin configuration is stored
      secretName: "airbyte-auth-secrets"
      # -- The first name of the initial user
      firstName: ""
      # -- The last name of the initial user
      lastName: ""
      # -- The key within `emailSecretName` where the initial user's email is stored
      emailSecretKey: "instance-admin-email"
      # -- The key within `passwordSecretName` where the initial user's password is stored
      passwordSecretKey: "instance-admin-password"```
but it failed to use the specified password but a random generated one

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1724180633419719) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["k8s", "secret.yaml", "authentication", "password", "airbyte", "platform", "bug"]
</sub>
2

the latest version of abctl now supports setting the email and password through the credentials command. abctl local credentials --password &lt;new_password&gt;

3

Right, but there’s no way for us to retrieve the creds from secrets.yaml or even secret manager? Because if we do re-spin the k8s, means we would need to set it again, correct?

4

And does the credentials is surfaced from the database itself?

5

Yes, if you install onto a new VM you will need to reset your credentials. Nothing obviously looks wrong with your values.yaml file, you are missing the global: section at the top but I did not know if that was just a copy paste error.

6

If you have already run an install and want to change the value of the secret, you will need to restart the airbyte-server with: kubectl rollout restart deployment/airbyte-abctl-server -n airbyte-abctl

7

Also you should not need to edit the values.yaml file if you just wish to set the password and clientId & secret. You can create a secret.yaml file like:

kind: Secret
metadata:
  name: airbyte-auth-secrets
stringData:
  instance-admin-client-id: foo
  instance-admin-client-secret: bar
  instance-admin-password: foobar
type: Opaque```
then run:
`abctl local install --secret ./secret.yaml` and that will set those values, again if abctl is already running, do the rollout restart of the airbyte-server deployment
8

Hey <@U065RJ879QT>, curious if you know any info on the above? Would be such a great help

9

No clue :upside_down_face: <@U07C8CCC68Y> should know!