gitea/helm-chart
45
54
Fork 126
Code Issues 32 Pull Requests 8 Actions Releases 87 Activity

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

Merged
lunny merged 3 commits from fix-admin-user-creation into master 2020-12-10 09:16:14 +00:00
Conversation 2 Commits 3 Files Changed 3 +14 -2
luhahn commented 2020-12-08 09:38:25 +00:00
Member
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 added 2 commits 2020-12-08 09:38:25 +00:00
Fix admin user creation for gitea 1.13.0
All checks were successful
continuous-integration/drone/push Build is passing
Details
e453147f4f
Add load balancer hint for ssh in README
All checks were successful
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/pr Build is passing
Details
623e9d38b7
luhahn commented 2020-12-08 09:40:49 +00:00
Author
Member
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 changed title from Fix admin user creation for gitea 1.13.0, chart version 2.1.0 to WIP: Fix admin user creation for gitea 1.13.0, chart version 2.1.0 2020-12-08 10:37:27 +00:00
luhahn changed title from WIP: Fix admin user creation for gitea 1.13.0, chart version 2.1.0 to Fix admin user creation for gitea 1.13.0, chart version 2.1.0 2020-12-08 16:44:49 +00:00
luhahn commented 2020-12-08 16:45:18 +00:00
Author
Member
Copy Link

This is needed for 1.13.0 admin creation

This is needed for 1.13.0 admin creation
luhahn added 1 commit 2020-12-09 07:22:00 +00:00
Merge branch 'master' into fix-admin-user-creation
All checks were successful
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/pr Build is passing
Details
d34cb8cfd7
zeripath approved these changes 2020-12-10 09:01:11 +00:00
Dismissed
lunny approved these changes 2020-12-10 09:16:08 +00:00
Dismissed
lunny merged commit 5311243a6e into master 2020-12-10 09:16:14 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
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
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
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gitea/helm-chart#80
No description provided.
Delete Branch "fix-admin-user-creation"

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?