Sign inSign up

aipipeline/kubeclient

By aipipeline

Updated over 3 years ago

Image
1

10K+

aipipeline/kubeclient repository overview

kubectl-wrapper

Wrapper kubectl in container. it should work as step of Tekton-pipeline, the goal is to operate(create, delete, apply, patch, replace) on k8s resources.

Inputs

Parameters
  • action: The action to perform to the resource, support get, create, apply, delete, replace, patch.
  • manifest: The content of the resource to deploy.
  • success-condition/failure-condition: SuccessCondition and failureCondition are optional expressions which are evaluated upon every update of the resource. If failureCondition is ever evaluated to true, the step is considered failed. Likewise, if successCondition is ever evaluated to true the step is considered successful. It uses kubernetes label selection syntax and can be applied against any field of the resource (not just labels). Multiple AND conditions can be represented by comma delimited expressions. For more details, see: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/.
  • merge-strategy: The strategy used to merge a patch, defaults to strategic, supported strategic, merge and json.
  • output: Extracted from fields of the resource, only support jsonpath. Should define as a yaml array(array even if only one item):
  - name: output
    value: |
      - name: job-name
        valueFrom: '{.metadata.name}'
      - name: job-namespace
        valueFrom: '{.metadata.namespace}' 

The extracted value will be write to/tekton/results/$(name).

  • set-ownerreference: Set the ownerReferences for the resource as pod of step, default to false.

Tag summary

Content type

Image

Digest

sha256:7834fefd3

Size

1 GB

Last updated

over 3 years ago

docker pull aipipeline/kubeclient