GithubHelp home page GithubHelp logo

Comments (6)

ericchiang avatar ericchiang commented on August 14, 2024

Couple thoughts on how this might go:

  • Document how to use an authenticating/authorizing proxy
  • Add instructions for running the registry as an aggregated API server while delegating auth-Z to the central API server
  • Define CRDs equivalents with JSON schema validation to let users register cluster objects on a existing cluster and just use RBAC

The more the cluster-registry repo can avoid re-implementing an API server, I think the better.

from cluster-registry.

pmorie avatar pmorie commented on August 14, 2024

Define CRDs equivalents with JSON schema validation to let users register cluster objects on a existing cluster and just use RBAC

This shouldn't be necessary - you can write an RBAC rule for any API group and resource/subresources. If you have delegating authn/z back to the main API server you will just get this.

@font what do you think about implementing this?

from cluster-registry.

perotinus avatar perotinus commented on August 14, 2024

Changed the name of this issue to specifically address delegated authorization. I opened #46 to track non-delegated authorization.

from cluster-registry.

font avatar font commented on August 14, 2024

Yes, I am working on this (realized I hadn't replied yet).

from cluster-registry.

font avatar font commented on August 14, 2024

How do we want to handle the different personalities that clusterregistry will assume when running as a delegated vs standalone apiserver?

Some things that will need to be addressed:

  • Authn model: currently CR has built-in authn model. Will also need to delegate to core k8s apiserver. Need to allow both.
  • Authz model: currently CR has always-allow authz model. Will also need to delegate to core k8s apiserver. Need to allow both.
  • Necessary flags: introducing new standalone flag while removing unnecessary flags when delegating
  • Other stuff?

Some possible options:

  • Add extra flag error checking and allow possible confusion when user specifies combinations that are not compatible.
  • Do we want to add new subcommands to handle the different flags that could then trigger different paths for the authn/authz setup? This would seem strange for an apiserver. Are there any other apiservers doing this?
  • Two separate binaries for delegated vs standalone. Probably try to avoid this.
  • Other options?

from cluster-registry.

perotinus avatar perotinus commented on August 14, 2024

This is now implemented and working as of #120.

from cluster-registry.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.