Define scope of the project

[hjacobs]

There are some parts of the project which might be out of scope:

• cloud-provider authentication (GCP, EKS, ..) --- this should probably be more a plugin than part of the core library
• high level workflow functionality (e.g. rolling update procedures)
• ...

TBD

[steinnes]

I'd like to port my EKS authentication from https://github.com/steinnes/pykubeks/ over to this project, however I am unclear on how you'd like this to be implemented as a plugin? I'd rather not start contributing only to have to refactor heavily later.

[hjacobs]

@steinnes that would be awesome, I haven't thought about it yet, but using native Python plugins like https://packaging.python.org/guides/creating-and-discovering-plugins/#using-package-metadata should work. So we just need to define some standard "interface" which is called from Pykube to support other auth mechanisms. WDYT?

[steinnes]

That seems like a fine place to start.

I'll take a look and see how it goes!

On Fri, Aug 30, 2019 at 6:33 PM Henning Jacobs [email protected] wrote:

@steinnes https://github.com/steinnes that would be awesome, I haven't thought about it yet, but using native Python plugins like https://packaging.python.org/guides/creating-and-discovering-plugins/#using-package-metadata should work. So we just need to define some standard "interface" which is called from Pykube to support other auth mechanisms. WDYT?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hjacobs/pykube/issues/6?email_source=notifications&email_token=AAIL63UAAC6V6ATBJHERCVDQHFRYRA5CNFSM4G3MLO7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5SOAHI#issuecomment-526704669, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIL63UJ6XJ7T56ZPNTLP7DQHFRYRANCNFSM4G3MLO7A .