Skip to content

Milestones

List view

  • Updated to kubebuilder v2 https://github.com/kubernetes-sigs/kubebuilder

    No due date
    21/21 issues closed
  • Extend the console resource to enable authorisation rules, permitting an approval process for getting access to consoles. As an example of the UX: ``` $ anu consoles create --repo payments-service --env live-staging -- bash INFO[0000] Connecting to Kubernetes... source="consoles_create.go:95" INFO[0000] Creating console... source="consoles_create.go:108" INFO[0000] Console has been requested console=paysvc-live-default-a1b2c namespace=production pod= source="consoles.go:117" This console is currently pending authorisation (rule: default). An authorisation is required from 1 members of: - [email protected] (GoogleGroup) Send this command to an authoriser: anu consoles authorise --context prd --namespace production --name paysvc-live-default-a1b2c Waiting for authorisation... ``` While the rules would be configured on console template resources, like so: ```jsonnet consoles.authorisationRule.new( name='say-whatever-in-ruby', command=['bundle', 'exec', 'rails', 'runner', 'puts(ARGV[0])', '*'], required=0, ), ```

    No due date
    25/25 issues closed