Skip to content
This repository has been archived by the owner on Oct 3, 2020. It is now read-only.

Define scope of the project #6

Open
hjacobs opened this issue Mar 3, 2019 · 3 comments
Open

Define scope of the project #6

hjacobs opened this issue Mar 3, 2019 · 3 comments

Comments

@hjacobs
Copy link
Owner

hjacobs commented Mar 3, 2019

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
Copy link

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
Copy link
Owner Author

hjacobs commented Aug 30, 2019

@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
Copy link

steinnes commented Aug 31, 2019 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants