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
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.
Spec.Github.organizationattribute should be set to the organization hosting the stacks in the remote GitHub repository. In the example above, the organization name is
Spec.Github.teamsattribute 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.
Spec.Github.apiUrlattribute should be set to the API URL for the remote GitHub repository being used. For example, the API URL for
A modified Kabanero CR instance for an application stack repository located in the
my_orgorganization of the
github.example.comGitHub repository using release
0.6.0of stacks might look like this:
Note: Avoid using the OpenShift Console to edit the Kabanero CR instance. The console may change the
apiVersion of the Kabanero CR instance from
v1alpha1. There is a description of the issue here.