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

Add Kubectl sample, porting from version "v1alpha1" #278

Merged
merged 1 commit into from
Apr 15, 2020

Conversation

vincent-pli
Copy link
Member

Fix issue: #233 , Porting from v1alpha1

Use a image with kubectl installed, we can setup step of task in tekton to create arbitrary rsource of kubernates.

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.

@googlebot googlebot added the cla: yes CLA has been signed label Apr 15, 2020
@tekton-robot tekton-robot requested review from chmouel and a user April 15, 2020 08:25
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Apr 15, 2020
@vincent-pli
Copy link
Member Author

/assign @vdemeester

description: Kubectl wrapper image
steps:
- name: kubeconfig
image: $(inputs.params.image)
Copy link
Member

Choose a reason for hiding this comment

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

This needs to a $(params.image) instead 😉

Copy link
Member Author

Choose a reason for hiding this comment

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

oh, my mistake, thanks 👍

- name: kubeconfig
image: $(inputs.params.image)
script: |
echo "$(inputs.params.manifest)" > /tmp/resource.yaml
Copy link
Member

Choose a reason for hiding this comment

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

$(params.manifest) here

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

Use a image with `kubectl` installed, we can setup `step` of `task` in tekton to create arbitrary rsource of kubernates.
@vincent-pli
Copy link
Member Author

/test pull-tekton-catalog-integration-tests

Copy link
Member

@vdemeester vdemeester 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 Apr 15, 2020
@tekton-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 15, 2020
@tekton-robot tekton-robot merged commit 82514c4 into tektoncd:v1beta1 Apr 15, 2020
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
name: default-admin
Copy link
Member

Choose a reason for hiding this comment

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

This seems like dangerous default behavior to recommend to users.

This grants the default SA (which runs every Pod in the cluster unless otherwise specified), complete cluster-admin access.

Can we either:

  1. Make it clearer to users that this is only intended forr insecure/non-critical use cases, and should be modified after installation to match the user's use case and needs, and/or
  2. Provide a more scoped-down role binding initially, which users can add to as they need?

Copy link
Member Author

Choose a reason for hiding this comment

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

@imjasonh
Thanks for the comments, it's make sense, I will work for a pr for it.

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. cla: yes CLA has been signed lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants