package kubecaml

  1. Overview
  2. Docs
Legend:
Library
Module
Module type
Parameter
Class
Class type
module Local_subject_access_review : sig ... end

Local_subject_access_review checks whether or not a user or group can perform an action in a given namespace. Having a namespace scoped resource makes it much easier to grant namespace scoped policy that includes permissions checking.

module Non_resource_attributes : sig ... end

Non_resource_attributes includes the authorization attributes available for non_resource requests to the Authorizer interface

module Non_resource_rule : sig ... end

Non_resource_rule holds information that describes a rule for the non_resource

module Resource_attributes : sig ... end

Resource_attributes includes the authorization attributes available for resource requests to the Authorizer interface

module Resource_rule : sig ... end

Resource_rule is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.

module Self_subject_access_review : sig ... end

Self_subject_access_review checks whether or the current user can perform an action. Not filling in a spec.namespace means "in all namespaces". Self is a special case, because users should always be able to check whether they can perform an action

module Self_subject_access_review_spec : sig ... end

Self_subject_access_review_spec is a description of the access request. Exactly one of Resource_authorization_attributes and Non_resource_authorization_attributes must be set

module Self_subject_rules_review : sig ... end

Self_subject_rules_review enumerates the set of actions the current user can perform within a namespace. The returned list of actions may be incomplete depending on the server's authorization mode, and any errors experienced during the evaluation. Self_subject_rules_review should be used by Uis to show/hide actions, or to quickly let an end user reason about their permissions. It should Not Be used by external systems to drive authorization decisions as this raises confused deputy, cache lifetime/revocation, and correctness concerns. Subject_access_review, and Local_access_review are the correct way to defer authorization decisions to the Api server.

module Self_subject_rules_review_spec : sig ... end
module Subject_access_review : sig ... end

Subject_access_review checks whether or not a user or group can perform an action.

module Subject_access_review_spec : sig ... end

Subject_access_review_spec is a description of the access request. Exactly one of Resource_authorization_attributes and Non_resource_authorization_attributes must be set

module Subject_access_review_status : sig ... end

Subject_access_review_status

module Subject_rules_review_status : sig ... end

Subject_rules_review_status contains the result of a rules check. This check can be incomplete depending on the set of authorizers the server is configured with and any errors experienced during evaluation. Because authorization rules are additive, if a rule appears in a list it's safe to assume the subject has that permission, even if that list is incomplete.