Check out what's in the latest release of Kabanero Learn More

Configuring Kabanero CLI service authorization

You can modify your Kabanero CR instance to provide authorization to the teams in GitHub that will administer the application stacks. If you do not already have a team defined, see Creating a team.

To provide authorization:
  • The Spec.Github.organization attribute should be set to the organization hosting the stacks in the remote GitHub repository. In the example above, the organization name is my_org.

  • The Spec.Github.teams attribute should be set to a yaml list of GitHub teams in the remote GitHub repository, whose members can administer the stack using the Kabanero CLI.

  • The Spec.Github.apiUrl attribute should be set to the API URL for the remote GitHub repository being used. For example, the API URL for github.com is https://api.github.com.

    A modified Kabanero CR instance for an application stack repository located in the my_org organization of the github.example.com GitHub repository using release 0.6.0 of stacks might look like this:

    apiVersion: kabanero.io/v1alpha2
    kind: Kabanero
    metadata:
      name: kabanero
      namespace: kabanero
    spec:
      stacks:
        repositories:
        - name: custom
          https:
            url: https://github.example.com/my_org/stacks/releases/download/0.6.0/incubator-index.yaml
      github:
        organization: my_org
        teams:
          - stack-admins
          - admins
        apiUrl: https://api.github.com

Note: Avoid using the OpenShift Console to edit the Kabanero CR instance. The console may change the apiVersion of the Kabanero CR instance from v1alpha2 to v1alpha1. There is a description of the issue here.

Edit This Page