Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Installation Guide for Google Cloud #948

Open
2 tasks done
mrappard opened this issue Oct 16, 2024 · 1 comment
Open
2 tasks done

Bug: Installation Guide for Google Cloud #948

mrappard opened this issue Oct 16, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@mrappard
Copy link

mrappard commented Oct 16, 2024

Describe the bug

At section 4 of (https://surrealdb.com/docs/surrealdb/deployment/google)

Connect to the cluster and define the initial credentials:

$ export SURREALDB_URL=http://$(kubectl get ingress surrealdb-tikv -o json | jq -r .status.loadBalancer.ingress[0].ip)
$ surreal sql -e $SURREALDB_URL
> DEFINE USER root ON ROOT PASSWORD 'StrongSecretPassword!' ROLES OWNER;

There was a problem with the database: There was a problem with the database: IAM error: Not enough permissions to perform this action

Verify you can connect to the database with the new credentials:
$ surreal sql -u root -p 'StrongSecretPassword!' -e $SURREALDB_URL
> INFO FOR ROOT
[{ namespaces: { }, users: { root: "DEFINE USER root ON ROOT PASSHASH '...' ROLES OWNER" } }]

You get an error, would it be possible to update the tutorial or can someone explain what I should do.

Steps to reproduce

Follow the Tutorial at (https://surrealdb.com/docs/surrealdb/deployment/google)

Expected behaviour

The new Password to be created

Contact Details

[email protected]

Is there an existing issue for this?

  • I have searched the existing issues

Code of Conduct

  • I agree to follow this project's Code of Conduct
@mrappard mrappard added the bug Something isn't working label Oct 16, 2024
@Ekwuno
Copy link
Contributor

Ekwuno commented Oct 18, 2024

Hey @mrappard thanks for opening this issue. I am assuming you are on >=2.0 . This is caused by a known issue with our helm chart and it's being addressed in these two PRs: surrealdb/helm-charts#9 & surrealdb/helm-charts#11.

Please bear with us as we address this issue.

@Ekwuno Ekwuno self-assigned this Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants