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

Research and document password management for community groups #3938

Open
parispittman opened this issue Jul 29, 2019 · 20 comments
Open

Research and document password management for community groups #3938

parispittman opened this issue Jul 29, 2019 · 20 comments
Assignees
Labels
area/community-management kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone

Comments

@parispittman
Copy link
Contributor

need a doc that describes the process and what platforms need to have credentials shared

example: zoom admins need to share the main account info

@parispittman parispittman added kind/documentation Categorizes issue or PR as related to documentation. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. labels Jul 29, 2019
@parispittman parispittman added this to the Next milestone Jul 29, 2019
@justaugustus
Copy link
Member

Interested in this as well for SIG Release assets.
I think @idvoretskyi mentioned CNCF has 1password?
/sig release

@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Jul 30, 2019
@idvoretskyi
Copy link
Member

@justaugustus LastPass.

It could be requested via the CNCF ServiceDesk (see https://github.com/cncf/servicedesk/blob/master/README.md#how-do-i-file-a-ticket-with-the-service-desk).

@justaugustus
Copy link
Member

Gotcha. Thanks Ihor!

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 28, 2019
@mrbobbytables
Copy link
Member

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 28, 2019
@idvoretskyi
Copy link
Member

/assign

I'm going to document this CNCF-wide during the next few weeks, which will be applicable for Kubernetes (obviously) as well.

@idvoretskyi
Copy link
Member

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 13, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 12, 2020
@nikhita
Copy link
Member

nikhita commented Jun 15, 2020

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jun 15, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 13, 2020
@markjacksonfishing
Copy link
Contributor

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 13, 2020
@mrbobbytables
Copy link
Member

/lifecycle frozen
Still a good idea, just no bandwidth for it.

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Sep 13, 2020
@mrbobbytables mrbobbytables changed the title doc: lastpass/password sharing process for mods/admins/community folks Research and document password management for community groups Oct 14, 2020
@castrojo castrojo self-assigned this Oct 14, 2020
@mrbobbytables mrbobbytables modified the milestones: Next, v1.20 Oct 14, 2020
@ameukam
Copy link
Member

ameukam commented Oct 16, 2020

@mrbobbytables Should we open a PR on https://github.com/1Password/1password-teams-open-source for an open source plan or do we need to use a Business Trial Plan for 1password evaluation ?

@mrbobbytables
Copy link
Member

mrbobbytables commented Oct 16, 2020

@ameukam open source plan :)

EDIT: To follow up. There are a few other nuances with it that need to be sorted out. Will update this thread with more information.

@jberkus
Copy link
Contributor

jberkus commented Jan 27, 2021

I'll endorse both 1Password (not OSS, but free to us) and Bitwarden (OSS) for PW-keeping from a user perspective. Both work well.

@coderanger
Copy link
Member

-1 for Bitwarden unless we have enough people on the infra team that actually know MSSQL and/or we confirm that it works with a hosted version of MSSQL that we can pay for or get donated. I don't think we want to bite off running that ourselves unless we have more expertise in it than I would expect.

@jberkus
Copy link
Contributor

jberkus commented Jan 28, 2021

@coderanger I was suggesting paying for their hosted version.

@ameukam
Copy link
Member

ameukam commented Jul 4, 2021

FYI : 1Password/for-open-source#359

@mrbobbytables mrbobbytables modified the milestones: v1.22, v1.23 Sep 20, 2021
@Debanitrkl
Copy link
Member

/area community-management

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/community-management kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/release Categorizes an issue or PR as relevant to SIG Release.
Development

No branches or pull requests