okteto / docs

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Registry Credentials documentaion

RinkiyaKeDad opened this issue · comments

In the UI the feature is called "Registry Credentials". If someone were to see this in the UI and search for it in the docs they might not land in the right place since in the docs it's under the privateRegistry heading. Either we should change the name in one of the places or maybe have a new page in docs called "Registry Credentials" with more info on how to configure them.

Untitled

@omnomagonz the goal of this feature is to deprecate privateRegistries, because privateRegistries forces you to add your credentials in plain and all Self-hosted users complain about this.
While we don't have UI to add the credentials from there, could we document how to directly create the CRD and point to those docs from "Registry Credentials"? I would also remove the privateRegistries references from our docs

@pchico83 Is creating the CRD something that needs to be documented independent of the new admin feature?

And for removing privateRegistries, would it still exist and we just don't recommend people use it or have we removed it in this feature work?

@pchico83 Is creating the CRD something that needs to be documented independent of the new admin feature?

@omnomagonz yes. credentials can be defined via the Okteto UI (implementation is delayed) or manually creating CRDs. Creating a CRD manually is independent from the UI docs.

And for removing privateRegistries, would it still exist and we just don't recommend people use it or have we removed it in this feature work?

Yes, we don't want breaking changes. But adding registry credentials via the UI (delayed) or a CRD is always better than using the helm section privateRegistries. That's why I think we should document CRDs and remove references to the helm privateRegistries section

Closing as this was already implemented