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.

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

Update README.md #15

Merged
merged 1 commit into from Aug 15, 2019
Merged

Update README.md #15

merged 1 commit into from Aug 15, 2019

Conversation

vincent-pli
Copy link
Member

This is a minimal steps which could make Operator works, draft version, please add item missing, thanks

Changes

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Release Notes

@tekton-robot tekton-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 9, 2019
README.md Outdated
The following steps will install [Tekton Pipeline](https://github.com/tektoncd/pipeline) and configure it appropriately for your cluster.
1. Create namespace: `tekton-operator`

`kubectl create namespace openshift-pipelines-operator`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kubectl create namespace tekton-operator

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, my mistake


`kubectl apply -f deploy/crds/*_crd.yaml`

3. Deploy the Operator
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

before deploying the operator image should be built. The image should be specified in the deploy/operator.yaml deployment manifest

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this is a problem. I think we need build an official image for it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I log a issue #16 to trace it

3. Deploy the Operator

`kubectl -n tekton-operator apply -f deploy/`

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I remember we have a demo saying we can either go with the auto-install or manual install of CR?
Shall we add the instruction on it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@houshengbo
Copy link

/retest

This is a minimal step which could make Operator works, draft version, please add item missing, thanks
Copy link
Member

@sthaha sthaha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 15, 2019
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sthaha, vincent-pli

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot merged commit 2273b82 into tektoncd:master Aug 15, 2019
nikhil-thomas pushed a commit to nikhil-thomas/tektoncd-operator that referenced this pull request Mar 29, 2021
piyush-garg pushed a commit to piyush-garg/operator that referenced this pull request Feb 6, 2024
Fix suffix name and lenght restrictions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants