lunny/helm-chart
1
0
Fork 1
Code Issues 36 Pull Requests 14 Actions Packages Projects Releases 93 Wiki Activity

Fix admin user creation for gitea 1.13.0, chart version 2.1.0 #80

Merged
luhahn merged 3 commits from refs/pull/80/head into master 2020-12-10 09:16:14 +00:00
Conversation 4 Commits 3 Files Changed 3 +14 -2
luhahn commented 2020-12-08 09:38:25 +00:00 (Migrated from gitea.com)
Copy Link
  • Fix admin user creation (#79)
  • Extend README with LoadBalancer hint for SSH (#72)

Even though this fixes the admin user creation for 1.13.0. It will not fix the admin users created before gitea 1.13.0 (Chart 2.1.0).

To fix those Admins you can:

  • Login to your gitea Container
  • Create another admin account
  • Login with new admin
  • Remove old admin from all organisations
  • Delete old admin
  • Rerun helm install or create your old admin again

After this the helm chart is upgradeable again and the admin user will persist.

Command to create a new admin user:

gitea admin create-user --username  myAdmin --password 'myPassword123 --email my@admin.com --admin --must-change-password=false

Please keep in mind, that I currently don't know why the existing admins are unable to login after the upgrade, so this is a workaround to get your admin back and prevention for those problems for new installations of gitea.

- Fix admin user creation (#79) - Extend README with LoadBalancer hint for SSH (#72) Even though this fixes the admin user creation for 1.13.0. It will not fix the admin users created before gitea 1.13.0 (Chart 2.1.0). To fix those Admins you can: - Login to your gitea Container - Create another admin account - Login with new admin - Remove old admin from all organisations - Delete old admin - Rerun helm install or create your old admin again After this the helm chart is upgradeable again and the admin user will persist. Command to create a new admin user: ```bash gitea admin create-user --username myAdmin --password 'myPassword123 --email my@admin.com --admin --must-change-password=false ``` Please keep in mind, that I currently don't know why the existing admins are unable to login after the upgrade, so this is a workaround to get your admin back and prevention for those problems for new installations of gitea.
luhahn commented 2020-12-08 09:40:49 +00:00 (Migrated from gitea.com)
Copy Link

Tested on my clusters:

  • With existing admins

  • Newly created admins

  • Admins created prior 1.13.0 will remain unavailable!

Tested on my clusters: - With existing admins - Newly created admins - Admins created prior 1.13.0 will remain unavailable!
luhahn commented 2020-12-08 16:45:18 +00:00 (Migrated from gitea.com)
Copy Link

This is needed for 1.13.0 admin creation

This is needed for 1.13.0 admin creation
zeripath (Migrated from gitea.com) approved these changes 2020-12-10 09:01:11 +00:00
lunny (Migrated from gitea.com) approved these changes 2020-12-10 09:16:08 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
zeripath
lunny
Labels
Clear labels
has/backport
in progress
invalid
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
need/backport
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/other
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lunny
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lunny/helm-chart#80
No description provided.
Delete Branch "refs/pull/80/head"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?