k8s-rbac-model
tekton-kickstarter
k8s-rbac-model | tekton-kickstarter | |
---|---|---|
1 | 3 | |
25 | 44 | |
- | - | |
0.0 | 0.0 | |
over 3 years ago | over 1 year ago | |
Makefile | Makefile | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
k8s-rbac-model
tekton-kickstarter
-
Cloud Native CI/CD with Tekton - Building Custom Tasks
# https://github.com/MartinHeinz/tekton-kickstarter/blob/master/misc/config.yaml apiVersion: v1 kind: ConfigMap metadata: name: repo-app-mapping data: repo-app-mapping.yaml: | '[email protected]:kelseyhightower/nocode.git': 'nocode' '[email protected]:MartinHeinz/blog-frontend.git': 'blog-backend' '[email protected]:MartinHeinz/game-server-operator.git': 'game-server-operator' '[email protected]:MartinHeinz/python-project-blueprint.git': 'sample-python-app' --- # https://github.com/MartinHeinz/tekton-kickstarter/blob/master/tasks/get-application-name/get-application-name.yaml apiVersion: tekton.dev/v1beta1 kind: ClusterTask metadata: name: get-application-name spec: params: - name: repository-url type: string - name: mapping-file type: string steps: - name: get-application-name image: mikefarah/yq script: | #!/usr/bin/env sh set -xe yq e '."$(params.repository-url)"' /config/$(params.mapping-file) | tr -d '\012\015' > /tekton/results/application-name results: - name: application-name # Can be accessed by other Tasks with $(tasks.get-application-name.results.application-name) workspaces: - name: config mountPath: /config
-
Cloud-Native CI/CD with Tekton - Laying The Foundation
Tekton is a versatile tool that can get quite complicated and therefore one short article definitely isn't enough to go over every piece of it in detail. This introduction should give you enough to get up and running with all the configurations in place. In the following articles in these series, we will explore how to use and build your own custom Tasks and Pipelines, deal with event handling - both HTTP events and scheduled with cron and much more. So, stay tuned for next article and in the meantime you can have a sneak peek at files in tekton-kickstarter repository where all the resources from this and following articles are already available. And in case you have some feedback or suggestion feel free to open an issue in the repository or just star it if like you the content. 😉
-
Cloud Native CI/CD with Tekton — Laying The Foundation
Article: https://itnext.io/cloud-native-ci-cd-with-tekton-laying-the-foundation-a377a1b59ac0 Repository: https://github.com/MartinHeinz/tekton-kickstarter
What are some alternatives?
chainmetric-network - Hyperledger Fabric network for IoT enabled permissioned blockchain with sensor requirements control Smart Contracts
gitlab-ci-local - Tired of pushing to test your .gitlab-ci.yml?
Gravitational Teleport - The easiest, and most secure way to access and protect all of your infrastructure.
pipeline - A cloud-native Pipeline resource.
nfs-operator - A Kubernetes NFS Operator based on Ansible Operator SDK
catalog - Catalog of shared Tasks and Pipelines.
k8s-mediaserver-operator - Repository for k8s Mediaserver Operator project
operator - Kubernetes operator to manage installation, updation and uninstallation of tektoncd projects (pipeline, …)
Blueprint/Boilerplate For Python Projects - Blueprint/Boilerplate For Python Projects
tekton-workshops - A small project for enabling teams and individuals to Tekton, with samples and use cases from real life scenarios.
community - Community documentation for the Tekton project
dive - A tool for exploring each layer in a docker image