Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Modify the section about installing in custom namespace #881

Merged
merged 1 commit into from
May 21, 2019
Merged

Modify the section about installing in custom namespace #881

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions DEVELOPMENT.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,12 +153,13 @@ kubectl create clusterrolebinding cluster-admin-binding \

1. To install into a different namespace you will need to modify resources in
the `./config` folder
- remove all `namespace: tekton` references from all yaml files
- delete the `namespace.yaml`
- modify the `metadata.name`
[here](https:/tektoncd/pipeline/blob/c1500fab83b09edadefb38bb8920a0c837d8f32b/config/100-namespace.yaml)
value to the desired namespace
- modify the `subjects.namespace`
[here](https:/tektoncd/pipeline/blob/c1500fab83b09edadefb38bb8920a0c837d8f32b/config/201-clusterrolebinding.yaml#L21)
value to the desired namespace
- look up all the lines with the namespace `namespace: tekton-pipelines`, and set the value to the desired namespace
- add `downwardapi` entry to webhook and controller `deployment` resources.
E.g. add the environment variable section from the code snippet below to
[controller](https:/tektoncd/pipeline/blob/c1500fab83b09edadefb38bb8920a0c837d8f32b/config/controller.yaml#L29)
Expand Down